Preprocessing of interlaced video with overlapped 3d transforms

ABSTRACT

In one method embodiment, partitioning a block matched reference frame into plural n×m non-overlapping pixel superblocks, where n and m are non-negative integer numbers; designating each of the n×m pixel superblocks as field or frame; and field processing by overlapped block processing logic two n×n blocks of an n×m overlapped superblock if one of first plural n×m superblocks intersected by the overlapped superblock has a field designation, otherwise frame processing, by the overlapped block processing logic, the two n×n blocks of the overlapped superblock.

TECHNICAL FIELD

The present disclosure relates generally to video noise reduction.

BACKGROUND

Filtering of noise in video sequences is often performed to obtain as close to a noise-free signal as possible. Spatial filtering requires only the current frame (e.g., picture) to be filtered and not surrounding frames in time. Spatial filters, when implemented without temporal filtering, may suffer from blurring of edges and detail. For this reason and the fact that video tends to be more redundant in time than space, temporal filtering is often employed for greater filtering capability with less visual blurring. Since video contains both static scenes and objects moving with time, temporal filters for video include motion compensation from frame to frame for each part of the moving objects to prevent trailing artifacts of the filtering.

BRIEF DESCRIPTION OF THE DRAWINGS

Many aspects of the disclosure can be better understood with reference to the following drawings. The components in the drawings are not necessarily to scale, emphasis instead being placed upon clearly illustrating the principles of the present disclosure. Moreover, in the drawings, like reference numerals designate corresponding parts throughout the several views.

FIG. 1 is a block diagram that illustrates an example environment in which certain embodiments of preprocessing sub-systems and methods of video denoising (VDN) systems and methods can be implemented.

FIGS. 2A-2C are schematic diagrams that conceptually illustrate processing implemented by various example embodiments of VDN systems and methods.

FIG. 3 is a block diagram that illustrates one example VDN system embodiment comprising frame alignment and overlapped block processing modules and respectively associated preprocessing sub-systems.

FIG. 4 is a block diagram that illustrates one example embodiment of a frame alignment module.

FIG. 5 is a block diagram that illustrates one example embodiment of a frame matching module, comprising example preprocessing sub-systems, of a frame alignment module.

FIG. 6A is a block diagram that illustrates example luma border pixel configurations applied by an embodiment of a staggered motion compensation sub-system residing in an example frame matching module.

FIG. 6B is a block diagram that illustrates an example constellation of a border configuration resulting from staggered motion compensation processing.

FIG. 7 is a block diagram that illustrates an overlapped superblock applied to an example field-frame map as implemented by a field-frame processing sub-system.

FIGS. 8A-8D are block diagrams that illustrate a modified one-dimensional (1D) transform used in an overlapped block processing module, the 1D transform illustrated with progressively reduced complexity.

FIG. 9 is a block diagram that conceptually illustrates the use of temporal modes in an overlapped block processing module.

FIG. 10 is a block diagram that illustrates an example mechanism for thresholding.

FIG. 11 is a block diagram that illustrates an example scene change detection mask utilized for detecting scene changes between matched frame pairs.

FIG. 12A is a flow diagram that illustrates an example method embodiment implemented by an embodiment of a field-frame processing sub-system in conjunction with an overlapped block processing module.

FIG. 12B is a flow diagram that illustrates another example method embodiment implemented by an embodiment of a field-frame processing sub-system in conjunction with an overlapped block processing module.

FIG. 13 is a flow diagram that illustrates an example method embodiment implemented by an embodiment of a scene change detection sub-system.

FIG. 14 is a flow diagram that illustrates an example method embodiment implemented by an embodiment of a staggered motion compensation sub-system.

DESCRIPTION OF EXAMPLE EMBODIMENTS

Overview

In one method embodiment, partitioning a block matched reference frame into plural n×m non-overlapping pixel superblocks, where n and m are non-negative integer numbers; designating each of the n×m pixel superblocks as field or frame; and field processing by overlapped block processing logic two n×n blocks of an n×m overlapped superblock if one of first plural n×m superblocks intersected by the overlapped superblock has a field designation, otherwise frame processing, by the overlapped block processing logic, the two n×n blocks of the overlapped superblock.

Example Embodiments

Disclosed herein are various example embodiments of preprocessing sub-systems and methods of a video denoising (VDN) system. One embodiment of a preprocessing sub-system, referred to herein as a field-frame processing (FFP) sub-system, comprises logic that simultaneously processes two interleaved n×n (e.g., 8×8) pixel sub-blocks of an n×m (e.g., 8×16) pixel superblock, where n and m are non-negative integer numbers. For a frame, a superblock is referred to herein as two vertically adjacent blocks (top/bottom), and for a field, a superblock is referred to herein as two interleaved blocks having a vertical span of two adjacent blocks. For purposes of brevity and for illustration only, each example luma superblock is described as having an 8×16 size, with the understanding that superblocks of other sizes (e.g., 16×32, etc.) as well as different-sized sub-blocks (i.e., the two blocks that make up a superblock) of a superblock are contemplated to be within the scope of the disclosure. The simultaneous, coupled processing for interlaced video as interleaved fields (e.g., single channel processing) as disclosed herein is in contrast to decoupled processing as two separate fields (e.g., splitting the two fields of frame pictures into separate channels), hence resulting in some implementations in reduced complexity. In one embodiment, the FFP sub-system provides (e.g., once for a reference frame) a field-frame map by logically partitioning a block matched frame into plural non-overlapping superblocks, the block matched frame destined to be denoised via an overlapped block process. For each superblock in the field-frame map, the FFP sub-system provides a respective frame or field designation. Based on the field-frame map and the coordinate position of an overlapped block (e.g., overlapped superblock) that is subject to comparison with the superblocks of the field-frame map, the FFP sub-system further determines whether the sub-blocks of the overlapped block at the particular coordinate position are to each undergo overlapped block processing (e.g., video denoising) as a frame or field.

Another embodiment of a preprocessing sub-system, referred to herein as a scene change detection (SCD) sub-system, comprises logic that provides a mechanism to detect scene changes and that further cooperates with mode decision logic that handles the detected scene change in one or more temporal depth modes. In one embodiment, the SCD sub-system is implemented during a block matching stage involving iterative respective sets of noise-filtered blocks from two full-size (e.g., not decimated) frames. As the iteration of block matching between the sets progresses, a decision is made, block-by-block, as to the closeness of the match until it is determined that a scene change detection has been triggered. In one embodiment, a bit mask is used to track the location of a detected scene change among a window of frames to facilitate implementation of a suitable temporal mode.

Yet another embodiment of a preprocessing sub-system, referred to herein as a staggered motion compensation (SMC) sub-system, comprises logic that applies a varying border configuration of pixels around a reference frame, the variation occurring between different pairings of the reference frame with another frame (and further difference in border configurations per fields of the same reference frame) in an intended block matching operation. In other words, each time a frame is matched to the reference frame, the same border configuration is used between the reference frame and the other frame, yet a different border is used for each pairing of the reference frame with another frame (and then removed at the completion of frame matching). The SMC sub-system effectively positions the seams of the n×m blocks for luma in different places each time a frame match is performed, eliminating or mitigating from the denoised frames blocking or other artifacts resulting from aggregated seams.

As indicated above, the various preprocessing sub-system embodiments are described in the context of a VDN system. In one embodiment, the VDN system comprises a frame alignment module and an overlapped block processing module, the overlapped block processing module configured to denoise video in a three-dimensional (3D) transform domain using motion compensated overlapped 3D transforms. In particular, certain embodiments of VDN systems motion compensate a set of frames surrounding a current frame, and denoise the frame using 3D spatio-temporal transforms with thresholding of the 2D and/or 3D transform coefficients. One or more VDN system embodiments provide several advantages or distinctive features over brute force methods of conventional systems, including significantly reduced computational complexity that enable implementation in real-time silicon (e.g., applicable to real-time applications, such as pre-processing of frames for real-time broadcasting of encoded pictures of a video stream), such as non-programmable or programmable hardware including field programmable gate arrays (FPGAs), and/or other such computing devices. Several additional distinctive features and/or advantages of VDN system embodiments, explained further below, include the decoupling of block matching and inverse block matching from an overlapped block processing loop, reduction of accumulation buffers from 3D to 2D+n (where n is an integer number of accumulated frames less than the number of frames in a 3D buffer), and the “collapsing” of frames (e.g., taking advantage of the fact that neighboring frames have been previously frame matched to reduce the amount of frames entering the overlapped block processing loop while obtaining the benefit of the information from the full scope of frames from which the reduction occurred for purposes of denoising). Such features and/or advantages enable substantially reduced complexity block matching. Further distinctive features include, among others, a customized-temporal transform and temporal depth mode selection, also explained further below.

These advantages and/or features, among others, are described hereinafter in the context of an example subscriber television network environment, with the understanding that other video environments may also benefit from certain embodiments of the preprocessing sub-systems and VDN systems and methods and hence are contemplated to be within the scope of the disclosure. It should be understood by one having ordinary skill in the art that, though specifics for one or more embodiments are disclosed herein, such specifics as described are not necessarily part of every embodiment.

FIG. 1 is a block diagram of an example environment, a subscriber television network 100, in which certain embodiments of preprocessing sub-systems of a VDN system may be implemented. The subscriber television network 100 may include a plurality of individual networks, such as a wireless network and/or a wired network, including wide-area networks (WANs), local area networks (LANs), among others. The subscriber television network 100 includes a headend 110 that receives (and/or generates) video content, audio content, and/or other content (e.g., data) sourced at least in part from one or more service providers, processes and/or stores the content, and delivers the content over a communication medium 116 to one or more client devices 118 through 120. The headend 110 comprises an encoder 114 having video compression functionality, and a pre-processor or VDN system 200 configured to receive a raw video sequence (e.g., uncompressed video frames or pictures), at least a portion of which (or the entirety) is corrupted by noise. Such noise may be introduced via camera sensors, from previously encoded frames (e.g., artifacts introduced by a prior encoding process from which the raw video was borne, among other sources). The VDN system 200 is configured to denoise each picture or frame of the video sequence and provide the denoised pictures or frames to the encoder 114, enabling, among other benefits, the encoder to encode fewer bits than if noisy frames were inputted to the encoder. In some embodiments, at least a portion of the raw video sequence may bypass the VDN system 200 and be fed directly into the encoder 114. The VDN system 200 further comprises a preprocessing sub-system 300, the pre-processing sub-system including, among other components or sub-systems described below, one or a combination of a field-frame processing (FFP) sub-system, scene change detection (SCD) sub-system, and/or staged motion compensation (SMC) sub-system as explained further below.

Throughout the disclosure, the terms pictures and frames are used interchangeably. In some embodiments, the uncompressed video sequences may be received in digitized format, and in some embodiments, digitization may be performed in the VDN system 200. In some embodiments, the VDN system 200 may comprise a component that may be physically and/or readily de-coupled from the encoder 114 (e.g., such as in the form of a plug-in-card that fits in a slot or receptacle of the encoder 114). In some embodiments, the VDN system 200 may be integrated in the encoder 114 (e.g., such as integrated in an applications specific integrated circuit or ASIC). Although described herein as a pre-processor to a headend component or device, in some embodiments, the VDN system 200 may be co-located with encoding logic at a client device, such as client device 118, or positioned elsewhere within a network, such as at a hub or gateway.

The headend 110 may also comprise other components, such as QAM modulators, routers, bridges, Internet Service Provider (ISP) facility servers, private servers, on-demand servers, multi-media messaging servers, program guide servers, gateways, multiplexers, and/or transmitters, among other equipment, components, and/or devices well-known to those having ordinary skill in the art. Communication of Internet Protocol (IP) packets between the client devices 118 through 120 and the headend 110 may be implemented according to one or more of a plurality of different protocols, such as user datagram protocol (UDP)/IP, transmission control protocol (TCP)/IP, among others.

In one embodiment, the client devices 118 through 120 comprise set-top boxes coupled to, or integrated with, a display device (e.g., television, computer monitor, etc.) or other communication devices and further coupled to the communication medium 116 (e.g., hybrid-fiber coaxial (HFC) medium, coaxial, optical, twisted pair, etc.) via a wired connection (e.g., via coax from a tap) or wireless connection (e.g., satellite). In some embodiments, communication between the headend 110 and the client devices 118 through 120 comprises bi-directional communication over the same transmission medium 116 by which content is received from the headend 110, or via a separate connection (e.g., telephone connection). In some embodiments, communication medium 116 may comprise of a wired medium, wireless medium, or a combination of wireless and wired media, including by way of non-limiting example Ethernet, token ring, private or proprietary networks, among others. Client devices 118 through 120 may henceforth comprise one of many devices, such as cellular phones, personal digital assistants (PDAs), computer devices or systems such as laptops, personal computers, set-top terminals, televisions with communication capabilities, DVD/CD recorders, among others. Other networks are contemplated to be within the scope of the disclosure, including networks that use packets incorporated with and/or compliant to other transport protocols or standards.

The VDN system 200 (and associated sub-systems, such as the preprocessing sub-system 300) may be implemented in hardware, software, firmware, or a combination thereof (collectively or individually also referred to herein as logic). To the extent certain embodiments of the VDN system 200 or a portion thereof are implemented in software or firmware, executable instructions or code for performing one or more tasks of the VDN system 200 are stored in memory or any other suitable computer readable medium and executed by a suitable instruction execution system. In the context of this document, a computer readable medium is an electronic, magnetic, optical, or other physical device or means that can contain or store a computer program for use by or in connection with a computer related system or method.

To the extent certain embodiments of the VDN system 200 or a portion thereof are implemented in hardware, the VDN system 200 may be implemented with any or a combination of the following technologies, which are all well known in the art: a discrete logic circuit(s) having logic gates for implementing logic functions upon data signals, an application specific integrated circuit (ASIC) having appropriate combinational logic gates, programmable hardware such as a programmable gate array(s) (PGA), a field programmable gate array (FPGA), etc.

Having described an example environment in which the VDN system 200 may be employed, attention is directed to FIGS. 2A-2C, which comprise schematic diagrams that conceptually illustrate data flows and/or processing implemented by various example embodiments of VDN systems and methods. Progressing from FIG. 2A to FIG. 2B and then to FIG. 2C represents a reduction in processing complexity, and hence like-processing throughout these three figures are denoted with the same numerical reference and an alphabetical or alphanumeric suffix (e.g., a, b, and c, or a-l, etc.) that may change from each figure for a given component or diagram depending on whether there is a change or reduction in complexity to the component or represented system 200. Further, each “F” (e.g., F0, F1, etc.) shown above component 220 a in FIG. 2A (and likewise shown and described in association with other figures) is used to denote frames that have not yet been matched to the reference frame (F4), and each “M” (e.g., M0, M1, etc.) is used to denote frames that have been matched (e.g., to the reference frame). Note that use of the term “component” with respect to FIGS. 2A-2C does not imply that processing is limited to a single electronic component, or that each “component” illustrated in these figures are necessarily separate entities. Instead, the term “component” in these figures graphically illustrates a given process implemented in the VDN system embodiments, and is used instead of “block,” for instance, to avoid confusion in the term, block, when used to describe an image or pixel block.

Overall, VDN system embodiment, denoted 200 a in FIG. 2A, can be subdivided into frame matching 210 a, overlap block processing 250 a, and post processing 270 a. In frame matching 210 a, entire frames are matched at one time (e.g., a single interval of time or single processing stage), and hence do not need to be matched during implementation of overlapped block processing 250 a. In other words, block matching in the frame matching process 210 a is decoupled (e.g., blocks are matched without block overlapping in the frame matching process) from overlapped block processing 250 a, and hence entire frames are matched and completed for a given video sequence before overlapped block processing 250 a is commenced for the given video sequence. By decoupling frame matching 210 a from overlapped block processing 250 a, block matching is reduced by a factor of sixty-four (64) when overlapped block processing 250 a has a step size of s=1 pixel in both the vertical and horizontal direction (e.g., when compared to integrating overlapped block processing 250 a with the frame matching 210 a). If the step size is s=2, then block matching is reduced by a factor of sixteen (16). One having ordinary skill in the art should understand that various step sizes are contemplated to be within the scope of the disclosure, the selection of which is based on factors such as available computational resources and video processing performance (e.g., based on evaluation of PSNR, etc.).

Shown in component 220 a are eight (8) inputted contiguous frames, F0(t) through F7(t) (denoted above each symbolic frame as F0, F1, etc.). The eight (8) contiguous frames correspond to a received raw video sequence of plural frames. In other words, the eight (8) contiguous frames correspond to a temporal sequence of frames. For instance, the frames of the raw video sequence are arranged in presentation output order (which may be different than the transmission order of the compressed versions of these frames at the output of the headend 110). In some embodiments, different arrangements of frames and/or different applications are contemplated to be within the scope of the disclosure. Note that quantities fewer or greater than eight frames may be used in some embodiments at the inception of processing. Frame matching is symbolized in FIGS. 2A-2C by the arrow head lines, such as represented in component 220 a (e.g., from F0 to F4, etc.).

As illustrated by the arrow head lines, frames F0(t) through F3(t) are matched to F4(t), meaning that blocks (e.g., blocks of pixels or image blocks, such as 8×8, 8×4, etc.) have been selected from those frames which most closely match blocks in F4(t) through a motion estimation/motion compensation process as explained below. The result of frame matching is a set of frames M0(t) through M7(t), where M4(t)=F4(t), as shown in component 230 a. Frames M0(t) through M7(t) are all estimates of F4(t), with M4(t)=F4(t) being a perfect match. M4(t) and F4(t) are used interchangeably herein.

Overlapped block processing 250 a is symbolically represented with components 252 (also referred to herein as a group of matched noisy blocks or similar), 254 (also referred to herein as 3D denoising or similar), 256 (also referred to as a group or set of denoised blocks or similar), and 260 a (also referred to herein as pixel accumulation buffer(s)). Overlapped block processing 250 a moves to a pixel location i,j in each of the matched frames (e.g., the same, co-located, or common pixel location), and for each loop, takes in an 8×8 noisy block b(i,j,t) (e.g., 240 a) from each matched frame M0 through M7, with the top left corner at pixel position i,j, so that b(i,j,t)=Mt(i:i+7, j:j+7). Note that i,j are vertical and horizontal indices which vary over the entire frame, indicating the position in the overlapped processing loop. For instance, for a step size s=1, i,j takes on every pixel position in the frame (excluding boundaries of 7 pixels). For a step size s=2 i,j takes on every other pixel. Further note that 8×8 is used as an example block size, with the understanding that other block sizes may be used in some embodiments of overlapped block processing 250 a. The group of eight (8) noisy 8×8 blocks (252) is also denoted as b(i,j, 0:7). Note that the eight (8) noisy blocks b(i,j, 0:7) (252) are all taken from the same pixel position i,j in the matched frames, since frame alignment (as part of frame matching processing 210 a) is accomplished previously. Frame matching 210 a is decoupled from overlapped block processing 250 a.

3D denoising 254 comprises forward and inverse transforming (e.g., 2D followed by 1D) and thresholding (e.g., 1D and/or 2D), as explained further below. In general, in 3D denoising 254, a 2D transform is performed on each of the 8×8 noisy blocks (252), followed by a 1D transform across the 2D transformed blocks. After thresholding, the result is inverse transformed (e.g., 1D, then 2D) back to pixel blocks. The result is a set of eight (8) denoised blocks bd(i,j, 0:7) (256).

For each loop, there are eight (8) denoised blocks (256), but in some embodiments, not all of the blocks of bd(i,j, 0:7) are accumulated to the pixel accumulation buffers 260 a, as symbolically represented by the frames and blocks residing therein in phantom (dashed lines). Rather, the accumulation buffers 260 a comprise what is also referred to herein as 2D+c accumulation buffers 260 a, where c represents an integer value corresponding to the number of buffers for corresponding frames of denoised blocks in addition to the buffer for A4. A 2D accumulation buffer corresponds to only A4 (the reference frame) being accumulated using bd(i,j,4) (e.g., denoised blocks bd(i,j,4) corresponding to frame A4 are accumulated). In this example, another buffer corresponding to c=1 is shown as being accumulated, where the c=1 buffer corresponds to denoised blocks bd(i,j,7) corresponding to frame AM7.

It follows that for an eight (8) frame window, a 2D+7 accumulation buffer equals a 3D accumulation buffer. Further, it is noted that using a 2D+1 accumulation buffer is analogous in the time dimension to using a step size s=4 in the spatial dimension (i.e. the accumulation is decimated in time). Accordingly, c can be varied (e.g., from 0 to a defined integer value) based on the desired visual performance and/or available computational resources. However, in some embodiments, a 3D accumulation buffer comprising denoised pixels from plural overlapped blocks is accumulated for all frames.

In overlapped block processing 250 a, blocks bd(i,j,4) and bd(i,j,7) are accumulated in accumulation buffers 260 a at pixel positions i,j since the accumulation is performed in the matched-frame domain, circumventing any need for inverse block matching within the overlapped block processing loop 250 a. Further, uniform weighting (e.g., w(i,j)=1 or no weighting at all) for all denoised blocks is implemented, which significantly reduces complexity. Note that in some embodiments, non-uniform weighting may be implemented. Note that in some embodiments, buffers for more than two frames (e.g., c>1) may be implemented. For a 2D+1 buffer, a frame begins denoising when it becomes A7, since there is an accumulation buffer for A7 for the 2D+1 accumulation buffer 260 a. A7 receives a second (2^(nd)) iteration of denoising when it becomes A4. The two are merged as shown in post-processing 270 a, as explained further below.

From the accumulation buffers 260 a, post processing 270 a is implemented, which comprises in one embodiment the processes of inverse frame matching 272 (e.g., as implemented in an inverse frame matching module or logic), delay 274 (e.g., as implemented in a delay module or logic), and merge and normalizing 276 (e.g., as implemented in merge and normalize module or logic). Since in one embodiment the accumulation buffer corresponding to AM7 is in the matched frame domain (e.g., frame 7 matched to frame 4), after the overlapped block processing is completed, data flow advances to inverse frame matching 272 to inverse frame match AM7(t) to obtain A7(t). As noted, this operation occurs once outside of overlapped block processing 250 a. A7(t) is then delayed (274), in this example, three frames, and merged (added) and normalized 276 to A4(t) (as represented by the dotted line arrowhead) to output FD4(t), the denoised frame. Had the inverse frame matching 272 been implemented in the overlapped block processing 250 a, the inverse frame matching would move a factor of sixty-four (64) more blocks than the implementation shown for a step size s=1, or a factor of 16 more for s=2.

Ultimately, after the respective blocks for each accumulated frame have been accumulated from plural iterations of the overlapped block processing 250 a, the denoised and processed frame FD4 is output to the encoder or other processing devices in some embodiments. As explained further below, a time shift is imposed in the sequence of frames corresponding to frame matching 210 a whereby one frame (e.g., F0) is removed and an additional frame (not shown) is added for frame matching 210 a and subsequent denoising according to a second or subsequent temporal frame sequence or temporal sequence (the first temporal sequence associated with the first eight (8) frames (F0-F7) discussed in this example). Accordingly, after one iteration of frame processing (e.g., frame matching 210 a plus repeated iterations or loops of overlapped block processing 250 a), as illustrated in the example of FIG. 2A, FD4(t) is output as a denoised version of F4(t). As indicated above, all of the frames F0(t) through F7(t) shift one frame (also referred to herein as time-shifted) so that F0(t+1)=F1(t), F1(t+1)=F2(t), etc., and a new frame F7(t+1) (not shown) enters the “window” (component 220 a) of frame matching 210 a. Note that in some embodiments, greater numbers of shifts can be implemented to arrive at the next temporal sequence. Further, F0(t) is no longer needed at t+1 so one frame leaves the window (e.g., the quantity of frames outlined in component 220 a). For the 8-frame case, as one non-limiting example, there is a startup delay of eight (8) frames, and since three (3) future frames are needed to denoise F4(t) and F5 through F7, there is a general delay of three (3) frames.

Referring now to FIG. 2B, shown is a VDN system embodiment, denoted 200 b, with further reduced computational complexity compared to the VDN system embodiment 200 a illustrated in FIG. 2A. The simplification in FIG. 2B is at least partially the result of the 2D+1 accumulation buffers 260 a and a modified 1D temporal transform, as explained further below. In the above-description of the 2D+1 accumulation buffers 260 a in FIG. 2A, it is noted that the 2D+1 accumulation buffers 260 a require only buffers (e.g., two) for denoised blocks, bd(i,j,4) and bd(i,j,7). Accordingly, a further reduction in complexity includes the “collapse” of the left four (4) frames, F0 through F3, into a single summation-frame FSUM, and frame-matching the summation-frame to F4, as illustrated in frame matching 210 b, and in particular, component 220 b of FIG. 2B. The collapse to a single summation frame comprises an operation which represents a close approximation to the left-hand side frame matching 210 a illustrated in FIG. 2A. Since F0 through F3 were previously matched together at time t−4, no matching operations are needed on those individual frames. Instead, frame matching 210 b matches the sum, FSUM, from time t−4 to F4, where

$\begin{matrix} {{{FSUM}\left( {t - 4} \right)} = {{\sum\limits_{j = 4}^{7}{{{Mj}\left( {t - 4} \right)}{{FSUM}\left( {t - 4} \right)}}} = {\sum\limits_{j = 4}^{7}{{{Mj}\left( {t - 4} \right)}.}}}} & {{Eq}.\mspace{14mu} (1)} \end{matrix}$

Eq. (1) implies that FSUM(t) is the sum of the four (4) frame-matched F4 through F7 frames, denoted M4(t) through M7(t) at time t, and is used four (4) frames (t−4) later as the contribution to the left (earliest) four (4) frames in the 3D transforms. A similar type of simplification is made with respect to frames F5 and F6. After the four (4) frames F0 through F3 are reduced to one FSUM frame, and F5 and F6 are reduced to a single frame, and then matched to F4(t), there are only four (4) matched frames, MSUM (actually MSUM0123), M4, M5+6, and M7, as noted in component 230 b, and therefore the entire overlapped block processing 250 b proceeds using just four (4) (b(i,j,4:7)) matched frames. The number of frames in total that need matching to F4(t) is reduced to three (3) in the VDN system embodiment 200 b of FIG. 2B from seven (7) in the VDN system embodiment 200 a in FIG. 2A. In other words, overlapped block processing 250 b receives as input the equivalent of eight (8) frames, hence obtaining the benefit of eight (8) frames using a fewer number of frame estimates.

FIG. 2C is a block diagram of a VDN system embodiment, 200 c, that illustrates a further reduction in complexity from the system embodiments in FIGS. 2A-2B, with particular emphasis at the accumulation buffers denoted 260 b. In short, the accumulation buffer 260 b comprises a 2D accumulation buffer, which eliminates the need for inverse motion compensation and reduces the complexity of the post-accumulating processing 270 b to a normalization block. In this embodiments, the frames do not need to be rearranged into the frame-matching (e.g., component 220 b) as described above in association with FIG. 2B. Instead, as illustrated in the frame matching 210 c, F7 is matched to F6, and the result is added together to obtain FSUM67. F5 is matched to F4 using the motion vectors from two (2) frames earlier (when F5, F4 were positioned in time at F7, F6 respectively), so this manner of frame matching is shown as a dotted line between F4 and F5 in component 220 c in FIG. 2C. As before, FSUM0123 represents four (4) frames matched, four (4) frames earlier, and summed together. In summary, frame matching 210 c for the 2D accumulation buffer 260 b matches three (3) frames to F4: FSUM0123, FSUM67 and F5.

Having described conceptually example processing of certain embodiments of VDN systems 200, attention is now directed to FIG. 3, which comprises a block diagram of VDN system embodiment 200 c-1. It should be understood by one having ordinary skill in the art in the context of the present disclosure that the various components shown in FIG. 3 may comprise, in one embodiment, software modules comprising code executed by a processor(s) (e.g., central processing unit or CPU, digital signal processor or DSP, etc.) of an FPGA or other device. In some embodiments, one or more of the components may be configured in hardware, or in some embodiments, the VDN system embodiment 200 may be configured as a mix of hardware and software components. It is noted that the architecture and functionality described hereinafter is based on VDN system embodiment 200 c described in association with FIG. 2C, with the understanding that similar types of architectures and components for VDN system embodiments 200 a and 200 b can be derived by one having ordinary skill in the art based on the teachings of the present disclosure without undue experimentation. VDN system embodiment 200 c-1 comprises a frame alignment module 310 that further comprises a staggered motion compensation (SMC) sub-system 300A and a scene change detection (SCD) sub-system 300B. The VDN system embodiment 200 c-1 further comprises a field-frame processing (FFP) sub-system 300C, the FFP sub-system comprising a field-frame mapping logic 380 and a field-frame logic 390, each of which are further described below. Note that in some embodiments, functionality for the field-frame mapping logic 380 and field-frame logic 390 may be combined, or in some embodiments, further distributed among a greater number of modules and/or combined with functionality of other modules. The VDN system embodiment 200 c-1 further comprises an overlapped block processing module 350 (that in one embodiment comprises, among other logic, the field-frame logic 390 of the field-frame processing sub-system 300C that cooperates with the field-frame mapping logic 380), an accumulation buffer 360, and a normalization module 370 (post-accumulation processing). It is noted that frame processing 250 in FIGS. 2A-2C correspond to the processing implemented by the frame alignment module 310, and overlap block processing 250 corresponds to the processing implemented by the overlapped block processing module 350. In addition, the 2D accumulation buffer 360 and the normalization module 370 implement processing corresponding to the components 260 and 270, respectively, in FIG. 2C. Note that in some embodiments, functionality may be combined into a single component or distributed among more or different modules.

As shown in FIG. 3, the frame alignment module 310 receives plural video frames F4(t), F6(t), and F7(t), where F4(t) is the earliest frame in time, and t is the time index which increments with each frame. The frame FSUM0123(t)=FSUM4567(t−4) represents the first four (4) frames F0(t) through F3(t) (F4(t−4) through F7(t−4)) which have been matched to frame F0(t) (F4(t−4)) previously at time t=t−4. The frame alignment module 310 produces the following frames for processing by the overlapped block processing module 350, the details of which are described below: M4(t), MSUM67(t), M5(t), and MSUM0123(t).

Before proceeding with the description of the overlapped block processing module 350, an example embodiment of the frame alignment module 310 is explained below and illustrated in FIG. 4. One example embodiment of a frame alignment module 310 a, shown in FIG. 4, receives frames F4(t), F6(t), F7(t), and FSUM0123(t). It is noted that M5(t) is the same as M76(t−2), which is the same as M54(t). F7(t) is frame-matched to F6(t) at frame match module 402, producing M76(t). After a delay (404) of two (2) frames, M76(t) becomes M54(t), which is the same as M5(t). Note that blocks labeled “delay” and shown in phantom (dotted lines) are intended to represent delays imposed by a given operation, such as access to memory. F6(t) is summed with M76(t) at summer 406, resulting in FSUM67(t). FSUM67(t) is frame-matched to F4(t) at frame match module 408, producing MSUM67(t). MSUM67(t) is multiplied by two (2) and added to F4(t) and M5(t) at summer 410, producing FSUM4567(t). FSUM4567(t) can be viewed as frames F5(t) through F7(t) all matched to F4(t) and summed together along with F4(t). FSUM4567(t) is delayed (412) by four (4) frames producing FSUM0123(t) (i.e., FSUM4567(t−4)=FSUM0123(t)). FSUM0123(t) is frame-matched to F4(t) at frame match module 414 producing MSUM0123(t). Accordingly, the output of the frame alignment module 310 a comprises the following frames: MSUM0123(t), M4(t), M5(t), and MSUM67(t).

One having ordinary skill in the art should understand in the context of the present disclosure that equivalent frame processing to that illustrated in FIG. 4 may be realized by the imposition of different delays in the process, and hence use of different time sequences of frames in a given temporal sequence as the input. For instance, an extra frame delay corresponding to the derivation of frames F6(t) and F7(t) from an FSUM87(t) may be inserted (e.g., immediately after summer 406), resulting in frames FSUM67(t), enabling all frame-matching operations to work out of memory.

One example embodiment of a frame match module, such as frame match module 402, is illustrated in FIG. 5. It should be understood that the discussion and configuration of frame match module 402 similarly applies to frame match modules 408 and 414, though not necessarily limited to identical configurations. Frame match module 402 comprises motion estimation (ME) and motion compensation (MC) functionality (also referred to herein as motion estimation logic and motion compensation logic, respectively), which is further subdivided into luma ME 502 (also luma ME logic or the like), chroma ME 504 (also chroma ME logic or the like), luma MC 506 (also luma MC logic or the like), and chroma MC 508 (also chroma MC logic or the like). In one embodiment, the luma ME 502 comprises a binomial filter 510 (also referred to herein as a pixel filter logic), a decimator 512 (also referred to herein as decimator logic), a decimated block matching (DECBM) module 514 (also referred to herein as decimated block matching logic), a full pixel bock matching (BM) module 516 (also referred to herein as full pixel block matching logic), and a luma refinement BM module 518. The chroma ME 504 comprises a chroma refinement BM module 520. The luma MC 506 comprises a luma MC module 522, and the chroma MC 508 comprises a chroma MC module 524.

The frame matching module 402 takes as input two video frames, each of which includes luminance and chrominance data in either of the well known CCIR-601 4:2:0 or 4:2:2 formats, though not limited to these formats, and in some embodiments may receive a proprietary format among other types of formats. For 4:2:0 formats, the chrominance includes two channels subsampled by a factor of two (2) in both the vertical and horizontal directions. For 4:2:2 formats, the chrominance is subsampled in only the horizontal direction. The luminance inputs are denoted in FIG. 5 as LREF and LF, which represent the reference frame luminance and a frame luminance to match to the reference, respectively. Similarly, the corresponding chrominance inputs are denoted as CREF (reference) and CF (frame to match to the reference). The output of the frame match process is a frame which includes luminance (LMAT) data and chrominance (CMAT) data. For instance, according to the embodiments described in association with, and illustrated in, FIGS. 2C, 3A, and 5, LREF, CREF, LF, CF and LMAT, CMAT correspond to the sets of frames given in Table 1 below:

TABLE 1 Sets of Frames Undergoing Frame Matching LREF, LMAT, CREF LF, CF CMAT Description F6(t) F7(t) M76(t) Frame Match F7(t) to F6(t) M76(t) is an estimate of F6(t) from F7(t) F4(t) FSUM67(t) MSUM67(t) Frame Match FSUM67(t) to F4(t) Normalize FSUM67(t) with divide by 2 prior to Frame Match. MSUM67(t) is an estimate of F4(t) from both F6(t) and F7(t) F4(t) FSUM0123(t) MSUM0123(t) Frame Match FSUM0123(t) to F4(t) Normalize FSUM(t − 4) with divide by 4 prior to Frame Match. MSUM0123(t) is an estimate of F4(t) from F0(t), F1(t), F2(t), F3(t) (or equivalently, F4(t − 4), F5(t − 4), F6(t − 4), F7(t − 4))

In general, one approach taken by the frame match module 402 is to perform block matching on blocks of pixels (e.g., 8×8) in the luminance channel, and to export the motion vectors from the block matching of the luminance channel for re-use in the chrominance channels. In one embodiment, the reference image LREF is partitioned into a set of 8×8 non-overlapping blocks. The final result of frame-matching is a set of motion vectors into the non-reference frame, LF, for each 8×8 block of LREF to be matched. Each motion vector represents the 8×8 block of pixels in LF which most closely match a given 8×8 block of LREF. The luminance pixels are filtered with a binomial filter and decimated prior to block matching.

The luma ME 502 comprises logic to provide the filtering out of noise, coarse block matching (using a multi-level or multi-stage hierarchical approach that reduces computational complexity) of the filtered blocks, and refined block matching using undecimated pixel blocks and a final motion vector derived from candidates of the coarse block matching process and applied to unfiltered pixels of the inputted frames. Explaining in further detail and with reference to FIG. 5, the luminance input (LREF, LF) is received at binomial filter 510, luma refinement BM module 518, and luma MC module 522. The binomial filter 510 processes the data and produces full-pixel luminance (BF_LF, BF_LREF), each of the luminance images of size N_(ver)×N_(hor). The binomial filter 510 performs a 2D convolution of each input frame according to the following equation:

$\begin{matrix} {{{{BF\_ X}\left( {i,j} \right)} = {\sum\limits_{m = {- 1}}^{1}{\sum\limits_{n = {- 1}}^{1}{{x\left( {m,n} \right)}{G\left( {{i - m},{j - n}} \right)}}}}},} & {{Eq}.\mspace{14mu} (2)} \end{matrix}$

where x(0: N_(ver)−1, 0: N_(hor)−1) is an input image of size N_(ver)×N_(hor), BF_X(i,j) is the binomial filtered output image, and G(m,n) is the 2D convolution kernel given by the following equation:

$\begin{matrix} {{G\left( {i,j} \right)} = {\frac{1}{16}\begin{pmatrix} 1 & 2 & 1 \\ 2 & 4 & 2 \\ 1 & 2 & 1 \end{pmatrix}}} & {{Eq}.\mspace{14mu} (3)} \end{matrix}$

Accordingly, LF and LREF are both binomial filtered according to Eq. (3) to produce BF_LF and BF_LREF, respectively, which are also input to the decimator 512 and the full BM module 516. Although a binomial filter is described as one example pixel filter, in some embodiments, other types of filters may be employed without undue experimentation, as should be understood by one having ordinary skill in the art.

BF_LF and BF_LREF are received at decimator 512, which performs, in one embodiment, a decimation by two (2) function in both the vertical and horizontal dimensions to produce BF_LF2 and BF_LREF2, respectively. The output of the decimator 512 comprises filtered, decimated luminance data (BF_LF2, BF_LREF2), where each of the luminance images are of size N_(ver)/2×N_(hor)/2. Thus, if the size of LF and LREF are both N_(ver)×N_(hor) pixels, then the size of BF_LF2 and BF_LREF2 are N_(ver)/2×N_(hor)/2 pixels. In some embodiments, other factors or functions of decimation may be used, or none at all in some embodiments.

The decimated, binomial-filtered luma pixels, BF_LF2 and BF_LREF2, are input to the DECBM module 514, which performs decimated block matching on the filtered, decimated data (BF_LF2, BF_LREF2). In one embodiment, the DECBM module 514 applies 4×4 block matching to the 4×4 blocks of BF_LREF2 to correspond to the 8×8 blocks of BF_LREF. In other words, the 4×4 pixel blocks in the decimated domain correspond to 8×8 blocks in the undecimated domain. The DECBM module 514 partitions BF_LREF2 into a set of 4×4 blocks given by the following equation:

$\begin{matrix} {{{{{BREF}\; 2\left( {i,j} \right)} = {{BF\_ LREF}\; 2\left( {{4\; {i:{{4\; i} + 3}}},{4\; {j:{{4\; j} + 3}}}} \right)}},{where}}{{i = 0},1,{{\ldots \mspace{14mu} \frac{N_{hor} - 1}{4}\mspace{14mu} {and}\mspace{14mu} j} = 0},1,{\ldots \mspace{14mu} {\frac{N_{ver} - 1}{4}.}}}} & {{Eq}.\mspace{14mu} (4)} \end{matrix}$

It is assumed that BF_LREF2 is divisible by four (4) in both the vertical and horizontal dimensions. The set of 4×4 blocks BREF2(i,j) in Eq. (4) includes all pixels of BF_LREF2 partitioned as non-overlapping 4×4 blocks. A function of the DECBM module 514 is to match each of these blocks to the most similar blocks in BF_LF2.

For each of the 4×4 blocks at BREF2(i,j), the DECBM module 514 searches, in one example embodiment, over a ±24 horizontal by ±12 vertical search area of BF_LF2 (for a total 49×25 decimated pixel area) to find 4×4 pixel blocks which most closely match the current 4×4 block. In some embodiments, differently configured (e.g., other than 24×12) search areas are contemplated. The search area of BF_LF2 is co-located with the block BREF2(i,j) to be matched. In other words, the search region BF_LF2_SEARCH(i, j) may be defined by the following equation:

BF _(—) LF2_SEARCH(i,j)=BF _(—) LF2(4i:4i±12,4j:4j±24)  Eq. (5)

Eq. (5) defines the search region as a function of (i j) that is centered at the co-located block BF_LF2(4i,4j) as in BF_LREF2(4i,4j), or equivalently BREF2(i,j). The search region may be truncated for blocks near the borders of the frame where a negative or positive offset does not exist. Any 4×4 block at any pixel position in BF_LF2_SEARCH(i,j) is a candidate match. Therefore, the entire search area is traversed extracting 4×4 blocks, testing the match, then moving one (1) pixel horizontally or one (1) pixel vertically. This operation is well-known to those with ordinary skill in the art as “full search” block matching, or “full search” motion estimation.

One matching criterion, among others in some embodiments, is defined as a 4×4 Sum-Absolute Difference (SAD) between the candidate block in BF_LF2 search area and the current BREF2 block to be matched according to Eq. 6 below:

${S\; A\; D\; 4\; x\; 4\left( {y,x} \right)} = {\sum\limits_{u = 0}^{3}{\sum\limits_{v = 0}^{3}{{{{BF\_ LF}\; 2\left( {{{4\; i} + y + u},{{4\; j} + x + v}} \right)} - {{BREF}\; 2\left( {{i + u},{j + v}} \right)}}}}}$

(Eq. (6)), where −24≦x≦24, −12≦y≦12. The values of y and x which minimize the SAD 4×4 function in Eq. (6) define the best matching block in BF_LF2. The offset in pixels from the current BREF2 block in the vertical (y) and horizontal (x) directions defines a motion vector to the best matching block. If a motion vector is denoted by my, then mv.y denotes the motion vector vertical direction, and mv.x denotes the horizontal direction. Note that throughout the present disclosure, reference is made to SAD and SAD computations for distance or difference measures.

It should be understood by one having ordinary skill in the art that other such difference measures, such as sum-squared error (SSE), among others well-known to those having ordinary skill in the art can be used in some embodiments, and hence the example embodiments described herein and/or otherwise contemplated to be within the scope of the disclosure are not limited to SAD-based difference measures.

In one embodiment, the DECBM module 514 may store not only the best motion vector, but a set of candidate motion vectors up to N_BEST_DECBM_MATCHES, where N_BEST_DECBM_MATCHES is a parameter having an integer value greater than or equal to one. For example, in one implementation, N_BEST_DECBM_MATCHES=3. As the DECBM module 514 traverses the search area, computing SAD 4×4 according to Eq. (6), the DECBM module 514 keeps track of the N_BEST_DECBM_MATCHES (e.g., minimum SAD 4×4 blocks) by storing the motion vectors (x and y values) associated with those blocks and the SAD 4×4 value. In one embodiment, a block is only included in the N_BEST_DECBM_MATCHES if its distance in either of the horizontal or vertical directions is greater than one (1) from any other saved motion vectors. The output of the DECBM module 514 is a set of motion vectors (MV_BEST) corresponding to N_BEST_DECBM_MATCHES, the motion vectors input to the full pixel BM module 516. In some embodiments, in addition to MV_BEST, the DECBM module 514 adds one or more of the following two motion vector candidates, if they are not already in the MV_BEST set: a zero motion vector and/or a motion vector of a neighboring block (e.g., a block located one row above). For example, if N_BEST_DECBM_MATCHES=3, meaning three (3) candidate motion vectors come from the DECBM module 514, then the total candidate motion vectors is five (5) (three (3) from the DECBM module SAD 4×4 operation plus a zero motion vector plus a neighboring motion vector). Therefore, in this example, if N_BEST_DECBM_MATCHES=3, then the total candidate motion vectors is five (5).

The DECBM module 514 omits from a search the zero vector (mv.x=0, mv.y=0) as a candidate motion vector output and any motion vectors within one pixel of the zero vector since, in one embodiment, the zero vector is always input to the next stage processing in addition to the candidate motion vectors from the DECBM module 514. Therefore, if N_BEST_DECBM_MATCHES=3, then the three (3) motion vectors consist of non-zero motion vectors, since any zero motion vectors are omitted from the search. Any zero-motion vector is included as one of the added motion vectors of the output of the DECBM module 514. In some embodiments, zero vectors are not input to the next stage and/or are not omitted from the search. The full pixel BM module 516 receives the set of candidate motion vectors, MV_BEST, and performs a limited, full pixel block matching using the filtered, undecimated frames (BF_LE, BF_LREF). In other words, the full pixel BM module 516 takes as input the motion vectors obtained in the DECBM module-implemented process, in addition to the zero motion vector and the motion vector from a neighboring block as explained above, and chooses a single refined motion vector from the candidate set. In some embodiments, a neighboring motion vector is not included as a candidate.

Operation of an embodiment of the full pixel BM module 516 is described as follows. The full pixel BM module 516 partitions BF_LREF into 8×8 blocks corresponding to the 4×4 blocks in BF_REF2 as follows:

BREF(i,j)=BF _(—) LREF(8i:8i+7,8j:8j+7),  Eq. (7)

where

${i = 0},1,{\ldots \mspace{14mu} \frac{N_{hor} - 1}{8}},{{{and}\mspace{14mu} j} = 0},1,{\ldots \mspace{14mu} {\frac{N_{ver} - 1}{8}.}}$

BREF is a set of non-overlapping 8×8 blocks comprising the entire luminance frame BF_LREF with a direct correspondence to the BREF2 4×4 blocks. The full pixel BM module 516 receives the MV_BEST motion vectors from the DECBM module 514 and the full pixel (undecimated), binomial filtered luminance BF_LREF and BF_LF.

The input, MV_BEST, to the full pixel BM module 516, may be denoted according to the following set: MV_BEST={mv_best(0), mv_best(1), . . . mv_best(N_BEST_DECBM_MATCHES−1)}. The full pixel BM module 516 scales the input motion vectors to full pixel by multiplying the x and y coordinates by two (2), according to Eq. (8) as follows:

mvfull(k).x=2×mv_best(k).x 0≦k<N_BEST_(—) DECBM_MATCHES,

mvfull(k).y=2×mv_best(k).y 0≦k<N_BEST_(—) DECBM_MATCHES  (Eq. (8))

where 0≦k≦N_BEST_DECBM_MATCHES−1. Note that the zero motion vector and neighboring block motion vector do not need scaling since zero does not need scaling, and the neighboring block motion vector is already scaled (sourced from the full pixel BM module 516). After scaling to full pixel, the full pixel BM module 516 determines a refined motion vector, mvrfull(k), from its corresponding candidate motion vector, mvfull(k), by computing a minimum SAD for 8×8 full-pixel blocks in a 5×5 refinement search around the scaled motion vector according to Eq. (9):

$\begin{matrix} {{S\; A\; D\; 8\; x\; 8\left( {i,j,{{{{mvfull}(k)} \cdot y} + m},{{{{mvfull}(k)} \cdot x} + n}} \right)} = {\sum\limits_{u = 0}^{7}{\sum\limits_{v = 0}^{7}{{{{BF\_ LF}\left( {{{8\; i} + {{{mvfull}(k)} \cdot y} + n + u},{{8\; j} + {{{mvfull}(k)} \cdot x} + m + v}} \right)} - {{BREF}\left( {{i + u},{j + v}} \right)}}}}}} & {{Eq}.\mspace{14mu} (9)} \end{matrix}$

where −2≦m≦2, −2≦n≦2. Note that one having ordinary skill in the art should understand in the context of the present disclosure that refinement search ranges other than 5×5 are possible and hence contemplated for some embodiments. Minimizing Eq. (9) for each motion vector of the candidate set results in (N_BEST_DECBM_MATCHES+2) refined candidate motion vectors, mvrfull(k), where 0≦k<(N_BEST_DECBM_MATCHES+2). The full pixel BM module 516 selects a final winning motion vector from the refined motion vectors by comparing the SAD of the refined motion vectors according to the following equation:

$\begin{matrix} {\lbrack{kf}\rbrack = {\underset{k}{Min}\left\{ {{\lambda*{{MVDIST}(k)}} + {{DISTBIAS}\mspace{11mu} (k)} + {{SAD}\; 8\; x\; 8\left( {i,j,{{{mvrfull}(k)} \cdot y},{{{mvrfull}(k)} \cdot x}} \right)}} \right\}}} & {{Eq}.\mspace{14mu} (10)} \end{matrix}$

where: kf=index of refined motion vector that is the winner; MVDIST(k)=min(dist(mvrfull(k), 0), dist(mvrfull(k), mvfull(B))); mvrfull(B)=winning motion vector of neighboring block; dist(a,b)=distance between motion vectors a and b; min(x,y)=minimum of x and y; DISTBIAS(k)=0 for MVDIST(k)<12, 20 for MVDIST(k)<20, 40 otherwise λ=operational parameter, e.g. λ=4

In other words, the larger the motion vector, the lower the SAD value to justify the larger motion vector as a winning candidate. For instance, winners comprising only marginally lower SAD values likely results in random motion vectors. The 12, 20, 40 values described above forces an increased justification (lower SAD values) for increasingly larger motion vectors. In some embodiments, other values and/or other relative differences between these values may be used (e.g., 1, 2, 3 or 0, 10, 20, etc.). Therefore, the final motion vector result from the full pixel block mode operation of full pixel BM module 516 is given by:

mvf(i,j).x=mvrfull(kf).x

mvf(i,j).y=mvrfull(kf).y  Eq. (11)

If the SAD value in Eq. (9) corresponding to the best motion vector of Eq. (11) is above a threshold, T_SAD, the block is flagged as a bad block (e.g., BAD_MC_BLOCK) so that instead of copying the block indicated by the motion vector in the search frame, the motion compensation process (described below) copies the original block of the reference frame instead.

The resultant output of the full pixel BM module 516 comprises a single final motion vector, MVF, for each non-overlapping block, which is input to the luma refinement BM module 518. The luma refinement BM module 518 (like the full pixel BM module 516) uses 8×8 block matching since it receives as input full (non-decimated) images. That is, the luma refinement BM module 518 refines the motion vectors using original unfiltered frame data (LREF, LF), or more specifically, takes as input the set of motion vectors MVF obtained in the full pixel BM module 516 and refines the motion vectors using original unfiltered pixels. Explaining further, the luma refinement BM module 518 partitions the original noisy LREF into 8×8 non-overlapping blocks corresponding to the 8×8 blocks in BF_REF according to the following equation:

REF(i,j)=LREF(8i:8i+7,8j:8j+7),  Eq. (12)

where

${i = 0},1,{\ldots \mspace{14mu} \frac{N_{hor} - 1}{8}},{{{and}\mspace{14mu} j} = 0},1,{\ldots \mspace{14mu} {\frac{N_{ver} - 1}{8}.}}$

REF is a set of non-overlapping 8×8 blocks comprising the entire luminance frame LREF with a direct correspondence to the BREF 8×8 blocks. For each block to be matched in REF, there is a motion vector from full pixel block mode operation of full pixel BM module 516 (e.g., mvf(i,j)). In one embodiment, a 1-pixel refinement around mvf(i,j) proceeds by the m and n which minimizes the following equation:

$\begin{matrix} {{S\; A\; D\; 8\; x\; 8\left( {i,j,{{{{mvf}\left( {i,j} \right)} \cdot y} + m},{{{{mvf}\left( {i,j} \right)} \cdot x} + n}} \right)} = {\sum\limits_{u = 0}^{7}{\sum\limits_{v = 0}^{7}{{{{LF}\left( {{{8\; i} + {{{mvf}\left( {i,j} \right)} \cdot y} + n + u},{{8\; j} + {{{mvf}\left( {i,j} \right)} \cdot x} + m + v}} \right)} - {{REF}\left( {{i + u},{j + v}} \right)}}}}}} & {{Eq}.\mspace{14mu} (13)} \end{matrix}$

where −1≦m≦−1, −1≦n≦−1. In some embodiments, pixel refinement other than by one (1-pixel) may be used in some embodiments, or omitted in some embodiments. The refined motion vector for the block at position i,j is given by the values of m and n, mref and nref respectively, which minimize Eq. (13). The refined motion vector is given by Eq. (14) as follows:

$\begin{matrix} {{{{{mvr}\left( {i,j} \right)} \cdot x} = {{{{mvf}\left( {i,j} \right)} \cdot x} + {mref}}}{{{{mvr}\left( {i,j} \right)} \cdot x} = {{{{mvf}\left( {i,j} \right)} \cdot x} + {mref}}}{{{{mvr}\left( {i,j} \right)} \cdot y} = {{{{mvf}\left( {i,j} \right)} \cdot x} + {nref}}}{{{{mvr}\left( {i,j} \right)} \cdot y} = {{{{mvf}\left( {i,j} \right)} \cdot x} + {nref}}}{where}{{i = 0},1,{\ldots \mspace{14mu} \frac{N_{hor} - 1}{8}},{{{and}\mspace{14mu} j} = 0},1,{\ldots \mspace{14mu} {\frac{N_{ver} - 1}{8}.}}}} & {{Eq}.\mspace{14mu} (14)} \end{matrix}$

MVRL (also referred to herein as refined motion vector(s)) denotes the complete set of refined motion vectors mvr(i,j) (e.g., for i=0, 8, 16, . . . N_(ver)−7; j=0, 8, 16, . . . N_(Hor)−7) for the luminance channel output from the luma refinement BM module 518. In other words, MVRL denotes the set of motion vectors representing every non-overlapping 8×8 block of the entire frame.

MVRL is used by the luma MC module 522 and the chroma refinement BM module 520. Referring to the chroma refinement BM module 520, the refined motion vectors, MVRL, are received at the chroma refinement BM module 520, which performs a refined block matching in the chrominance channel based on inputs CF and CREF. For 4:2:0 video formats, when the chroma is sub-sampled by a factor of two (2) in each of the horizontal and vertical dimensions, the chroma refinement BM module 520 performs 4×4 full-pixel block matching. That is, the chroma (both Cb and Cr) 4×4 blocks correspond directly to the luma 8×8 blocks. Using the MVRL input, the chroma refinement BM module 520, for both Cb and Cr chroma frames, performs a 1-pixel refinement around the MVRL input motion vectors in a similar manner to the process performed by the luma refinement BM module 518 described above, but using 4×4 blocks instead of 8×8, and a SAD 4×4 instead of SAD 8×8 matching criterion. The resulting set of motion vectors are MVRCb for Cb and MVRCr for Cr (collectively shown as MVRC in FIG. 5), which are input to the chroma MC module 524 to perform motion compensation.

Motion compensation is a well-known method in video processing to produce an estimate of one frame from another (e.g., to “match” one frame to another). MVRL and MVRC are input to motion compensation (MC) processes performed at luma MC module 522 and chroma MC module 524, respectively, which import the blocks indicated by the MVRL and MVRC motion vectors. With reference to the luma MC module 522, after the block matching has been accomplished as described hereinabove, the LF frame is frame-matched to LREF by copying the blocks in LF indicated by the motion vectors MVRL. For each block, if the block has been flagged as a BAD_MC_BLOCK by the full pixel BM module 516, instead of copying a block from the LF frame, the reference block in LREF is copied instead. For chroma operations, the same process is carried out in chroma MC module 508 on 4×4 blocks using MVRCb for Cb and MVRCr for Cr, and hence discussion of the same is omitted for brevity. Note that 8×8 and 4×4 were described above for the various block sizes, yet one having ordinary skill in the art should understand that in some embodiments, other block sizes than those specified above may be used.

Having described the overall operation of an embodiment of the frame match module 402, attention is now directed to the SMC sub-system 300A. In the block matching process, the 8×8 blocks (4×4 for chroma) are in the same pixel positions in the matched frames M0123, M5, and M67. Accordingly, the “seams” of the 8×8 blocks of the matched frames are in the same pixel positions. In circumstances where there exists a high level of filtering, some of these seams may become visible in the denoised frames. Further, every pixel is matched with a group of pixels in its designated block, so there is a bias for that pixel to be grouped with certain pixels. Even without the seams becoming visible, an undesirable blocking effect may become visible.

Certain embodiments of an SMC sub-system 300A implement a mechanism referred to herein as staggered motion compensation (SMC), which enables 8×8 blocks to be positioned in different positions in the M0123, M5 and M67 frames, and further, in the fields of these frames. As shown in example frame match module 402, SMC sub-system 300A comprises border add logic 526 and 528 at the input of the luma ME 502 and chroma ME 504, respectively, and border extract logic 530 and 532 at the output of the luma MC 506 and chroma MC 508, respectively. In general, the border add logic 526 receives the luma LF and LREF and outputs the corresponding frames to be matched with the added pixel borders to the binomial filter 510 and the luma refinement BM 518. The border add logic 528 receives the chroma CF and CREF and outputs the corresponding frames with the added pixels to the chroma refinement BM 520 and the chroma MC 524. The border extract logic 530 residing in one embodiment in the luma MC 506 receives the output from the luma MC 522 and strips away the added pixel border and outputs LMAT (without the border). Similarly, the border extract logic 532 of the chroma MC 508 receives the output from the chroma MC 524, strips away the added pixel border, and outputs CMAT (without the border). Each of the above-described logic (e.g., 526, 528, 530, and 532) of the SMC sub-system 300A receives border configuration (BC) signals from a processor (not shown) in or associated with the VDN system.

Explaining further, to accomplish SMC in one embodiment, a border is placed by the border add logic 526 and 528 around the frames to be matched (LF and LREF, CF and CREF in FIG. 5). The total amount of left border pixels plus the total amount of right border equals, in this example, eight (8) for luma and four (4) for chroma for any of the matching frames (and same for top/bottom border). For example, a border of 2-left, 6-right, 4-top, 4-bottom is one example luma border configuration signaled (e.g., by the BC or border_configuration) to the border add logic 526 of the SMC sub-system 300A. Note that the BC is downsampled by two (2) in the border add logic 528 so that the chroma effectively has the same BC as the luma. The border itself in one embodiment is simply black pixels. One having ordinary skill in the art should understand, in the context of the present disclosure, that other quantities of pixels may be used for the border.

For interlaced video, each field is block matched separately. Therefore, a tally of two (2) different border configurations per frame is contemplated in some embodiments, one for each field. For example, since M0123, M5 and M67 are the result of three (3) frame-matching operations, there may exist a total of six (6) border configurations (e.g., signalled to the SMC logic), putting the seams in six (6) different locations. Some example border configurations for luma are given in example Table 600 shown in FIG. 6A, which shows example pixel border configurations for the top, bottom, left, and right of each field frame to be matched. It should be appreciated, in the context of the present disclosure, that for these or other quantities of frame matching operations, a different quantity of border pixel configurations may be applied.

An example constellation 650 of the six (6) border configurations is shown in FIG. 6B (denoted symbolically by “X”). As shown, the border configurations of Table 600 evenly spread out the seams of the block matching process. It is further noted that the border configurations of Table 600 are all even amounts, since in at least one embodiment, the chroma block matching uses exactly the same border downsampled by two (2) to properly re-use motion vectors. Therefore, for chroma, the border configurations are the same as Table 600 divided by two (2). As an example, M5 for chroma on Field 1 (F1) uses [2,2,2,2]. Also note that the border size for chroma is four (4) pixels total for left-right, and four (4) pixels total for top/bottom. For progressive video, there is only one (1) large field, so only the F1 border configuration is used.

After block matching, the border is stripped away (e.g., removed) by the border extract logic 530 and 532 and has no effect on the rest of the overlapped block processing (e.g., is transparent to the overlapped block processing module 350).

With reference to FIG. 3, having described an example embodiment of the various modules or logic that comprise the frame alignment module 310 for the VDN system embodiment 200 c-1, attention is directed to the overlapped block processing module 350. In general, after frame matching, the overlapped block processing module 350 denoises the overlapped 3D blocks and accumulates the results, as explained in association with FIGS. 2A-2C. In one embodiment, looping occurs by stepping j by a step size s in pixels (e.g. s=2). The overlapped block processing moves horizontally until j==N_(Hor)−1, after which j is set to 0 and i is incremented by s. Note that in some embodiments, seven (7) pixels are added around the border of the frame to enable the border pixels to include all blocks. For simplicity, these pixels may be a DC value equal to the touching border pixel.

Before proceeding further on the discussion of the overlapped block processing loop, some VDN system embodiments include preprocessing sub-systems 300 that utilize single channel field processing as indicated above. Accordingly, in one embodiment, it is noted that an output of the frame alignment module 310 is provided to the field-frame processing (FFP) sub-system 300C. In one embodiment, for field-frame processing, the field-frame mapping logic 380 partitions (e.g., logically partitions) a matched frame into plural superblocks, each superblock comprising in one embodiment 8×16 non-overlapping pixel blocks (e.g., 8-pixel horizontal, 16-pixel vertical). An 8×16 non-overlapping pixel block comprises two (2) sub-blocks (e.g., each 8×8, collectively spanning sixteen (16) pixels vertically for luma). For chroma, both dimensions are halved, though in some embodiments, other integer decimations are contemplated for chroma processing. The field-frame mapping logic 380 of the FFP sub-system 300C provides (e.g., computes) a field-frame map (e.g., once) for the entire F4 frame with a binary indication 1=field, 0=frame for each of the non-overlapping 8×16 superblocks from the luma as explained below. The chroma processing uses the luma field-frame map, though in some embodiments, a separate field-frame map for chroma may be provided.

Let I(x,y) denote the luminance intensity for a pixel at position x, y for all non-overlapping superblocks at positions x=0, 16, 32, 48, . . . and y=0, 8, 16, 24, 32 . . . and compute A_(frame) A_(field) as follows:

$\begin{matrix} {A_{frame} = {\sum\limits_{x = 0}^{13}{\sum\limits_{y = 0}^{7}{{{I\left( {x,y} \right)} - {I\left( {{x + 1},y} \right)}}}}}} & (a) \\ {A_{field} = {\sum\limits_{x = 0}^{13}{\sum\limits_{y = 0}^{7}{{{I\left( {x,y} \right)} - {I\left( {{x + 2},y} \right)}}}}}} & (b) \end{matrix}$

Further, consider, A_(diff) given by:

A _(diff) =A _(frame) −A _(field)  (c)

If A_(diff)>TADIFF, then the 8×16 luma superblock is marked as a field block, otherwise the 8×16 luma superblock is marked as a frame block, where TADIFF is an operational parameter that may be set once at startup (e.g. TADIFF=50), or in some embodiments set more often and/or at different stages. One having ordinary skill in the art should understand, in the context of the present disclosure, that though equations (a) through (c) provide one method for determining a field or frame, other mechanisms known to those having ordinary skill in the art may be employed and hence are contemplated to be within the scope of the disclosure.

The field-frame map is used in the overlapped block processing (e.g., AVC-DCT, Haar, thresholding, Inverse, etc.) as explained in further detail below. In general, for each overlapped block, a field-frame indication is derived from the field-frame map. If the indication is field, then the two vertically interleaved 8×8 field blocks of the superblock are simultaneously processed by the overlapped block processing for luma. In other words, there is a direct coupling of the processing of fields, as opposed to splitting and processing as separate fields. If the indication is frame, then two 8×8 frame blocks (e.g., top/bottom) are processed for luma. As indicated above, for one embodiment, chroma processing uses the field-frame map generated for the F4 frame from luma and performs analogous processing on, in one embodiment, 4×4 fields for frame blocks. Note that at a time corresponding to completion of (e.g., after) the overlapped block processing, the denoised F4 blocks are accumulated in the appropriate position in the accumulation buffer (e.g., either as two vertically interleaved sub-blocks of the superblock or top/bottom adjacent sub-blocks of the superblock).

Explaining the above in further detail, it is noted that one complication in the transition from field-frame processing to overlapped block processing is that the field-frame map corresponds to field-frame indications for non-overlapping 8×16 superblocks, and as explained further below, overlapped block processing contains many more blocks due to the overlapping. As shown in FIG. 7, an overlapped block 702 (e.g., a superblock) intersects four (4) non-overlapping superblocks in the field-frame map 700. One approach implemented by the field-frame logic 380 of FIG. 3 comprises the following procedure: for each overlapped block 702, if the overlapped block position in the frame intersects any field blocks 704 (e.g., field-designated superblocks, where the field designation is represented by “F1” in FIG. 7) in the field-frame 700, the overlapped block 702 (e.g., the sub-blocks of the overlapped block or superblock 702) is marked for field processing. If the overlapped block position overlaps only frame blocks 706 (e.g., frame-designated superblocks, where the frame designation is represented by “FR” in FIG. 7) in the field-frame map 700, then the block 702 (e.g., the sub-blocks of the overlapped block or superblock 702) is marked for frame processing. For progressive video input, the field-frame map 700 is set to all ones (1s) indicating frame processing only.

Further, note that for a step size vertically (same as horizontally) of two (2) in the overlapped block processing, there are 4×4 or sixteen (16) overlapped blocks accumulated for all blocks except the borders. On the bottom border, both the bottom row of 8×8 blocks and the row immediately above have no vertical step, so these blocks (other than left/right borders) have four (4) blocks accumulated instead of sixteen (16). This situation arises because the overlapped processing works on 8×16 blocks, and it is not possible to shift vertically once the processing has reached the bottom sixteen (16) pixels of the frame.

Block matching (motion estimation and compensation) described hereinbefore is unaffected by field-frame processing, since all block matching proceeds on two independent fields (i.e., there is no field-frame in block matching). For progressive inputs, block matching proceeds using one large field per frame instead of two (2) fields (i.e., there is no field processing).

Referring again to FIG. 3, and assuming hereinafter frame processing (since if field processing is assumed, the only significant effect is that there should be a communication to the 2D buffer accumulation as to the presence of interleaved field blocks or top/bottom frame blocks to enable a determination of where to accumulate the blocks), the overlapped block processing module 350 receives the matched frames M4(t), M5(t), MSUM67(t), and MSUM0123(t), and extracts co-located blocks of 8×8 pixels from these four (4) frames. Denote the four (4) blocks extracted at a particular i, j pixel position in the four (4) frames as b(i, j, t) with t=0 . . . 3, then after reordering of the blocks (as explained below in the context of the 1D transform illustrated in FIGS. 8A-8D), the following terminology is described:

b(i, j, 0) is an 8×8 block from MSUM0123(t) at pixel position i, j b(i, j, 1) is an 8×8 block from M4(t) at pixel position i, j b(i, j, 2) is an 8×8 block from M5(t) at pixel position i, j b(i, j, 3) is an 8×8 block from MSUM67(t) at pixel position i, j

Starting with i=0 and j=0, the upper left corner of the frames, a 2D transform module 304 (also referred to herein as transform logic) extracts the four (4) blocks b(0, 0, 0:3) and performs a 2D transform. That is, the 2D transform is taken on each of the four (4) temporal blocks b(i, j, t) with 0≦t≦3, where i, j is the pixel position of the top left corner of the 8×8 blocks in the overlapped block processing. In some embodiments, a 2D-DCT, DWT, among other well-known transforms may be used as the spatial transform. In an embodiment described below, the 2D transform is based on an integer DCT defined in the Advanced Video Coding (AVC) standard (e.g., an 8×8 AVC-DCT), which has the following form:

H(X)=DCT(X)=C·X·C ^(T)  Eq. (15)

where,

$C = {\begin{bmatrix} 8 & 8 & 8 & 8 & 8 & 8 & 8 & 8 \\ 12 & 10 & 6 & 3 & {- 3} & {- 6} & {- 10} & {- 12} \\ 8 & 4 & {- 4} & {- 8} & {- 8} & {- 4} & 4 & 8 \\ 10 & {- 3} & {- 12} & {- 6} & 6 & 12 & 3 & {- 10} \\ 8 & {- 8} & {- 8} & 8 & 8 & {- 8} & {- 8} & 8 \\ 6 & {- 12} & 3 & 10 & {- 10} & {- 3} & 12 & {- 6} \\ 4 & {- 8} & 8 & {- 4} & {- 4} & 8 & {- 8} & 4 \\ 3 & {- 6} & 10 & {- 12} & 12 & {- 10} & 6 & {- 3} \end{bmatrix} \cdot {1/8}}$

X is an 8×8 pixel block, and the products on the right are matrix multiplies. One method for computing the DCT employs the use of signed powers of two for computing the multiplication products. In this way no hardware multipliers are needed; but rather, the products are created by shifts and additions thereby reducing the overall logic. In some embodiments, hardware multipliers may be used. In addition, scaling factors may be used, which may also reduce the required logic. To retrieve the original pixels (X), the integer matrix is scaled such that the inverse DCT implemented by the inverse 2D transform module 314 yields the original values of X. One form of the inverse AVC-DCT of the inverse transform module 314 comprises the following:

X=(C ^(T) ·H(X)·C)

S _(i,j),  Eq. (16)

or by substitution:

X=C _(s) ^(T) ·H(X)·C _(s),  Eq. (17)

where C_(s)=C

S_(i,j) and the symbol

denotes element by element multiplication. One example of scaling factors that may be used is given below:

$\begin{matrix} {S_{i,j} = {\frac{1}{\sum\limits_{i,{j = 0}}^{7}C_{({i,j})}^{2}} = \begin{matrix} 0.0020 \\ 0.0017 \\ 0.0031 \\ 0.0017 \\ 0.0020 \\ 0.0017 \\ 0.0031 \\ 0.0017 \end{matrix}}} & {{Eq}.\mspace{14mu} (18)} \end{matrix}$

After the 2D transform, the overlapped block processing module 350 changes the spatial dimension from 2D to 1D by zig-zag scanning the output of each 2D transform from low frequency to highest frequency, so the 2D transformed block bs(i, j, f) becomes instead bs(zz_index, f), where 0≦zz_index≦63, 0≦f≦3. The mapping of (i, j) to zz_index is given by the zig_zag_scan vector below, identical to the scan used in MPEG-2 video encoding. In some embodiments, the 2D dimension may be retained for further processing. If the first row of the 2D matrix is given by elements 0 through 7, the second row by 8 through 16, then zig_zag_scan[0:63] specifies a 2D to 1D mapping as follows:

zig_zag_scan[0:63] = {  0,1,8,16,9,2,3,10,17,24,32,25,18,11,4,5,  12,19,26,33,40,48,41,34,27,20,13,6,7,14,21,28,  35,42,49,56,57,50,43,36,29,22,15,23,30,37,44,51,  58,59,52,45,38,31,39,46,53,60,61,54,47,55,62,63 };

At a time corresponding to computation of the 2D transform (e.g., subsequent to the computation), the temporal mode (TemporalMode) is selected by temporal mode module 302 (also referred to herein as temporal mode logic). When utilizing a Haar 1-D transform, the TemporalMode defines whether 2D or 3D thresholding is enabled, which Haar subbands are thresholded for 3D thresholding, and which spatial subbands are thresholded for 2D thresholding. The temporal mode may either be SPATIAL_ONLY, FWD4, BAK4, or MODE8, as further described hereinbelow. The temporal mode is signaled to the 2D threshold module 306 and/or the 3D threshold module 310 (herein also collectively or individually referred to as threshold logic or thresholding logic). If the TemporalMode==SPATIAL_ONLY, then the 2D transformed block bs(zz_index, 1) is thresholded yielding bst(zz_index, 1). If the temporal mode is not SPATIAL_ONLY, then bst(zz_index, t) is set to bs(zz_index, f).

Following spatial thresholding by the 2D threshold module 306, the bst(zz_index, t) blocks are 1D transformed at the 1D transform module 308 (also referred to herein as transform logic), yielding bhaar(zz_index, f). The 1D transform module 308 takes in samples from the 2D transformed 8×8 blocks that have been remapped by zig-zag scanning the 2D blocks to 1D, so that bs(zz_index, f) represents a sample at 0≦zz_index≦63 and 0≦f≦3 so that the complete set of samples is bs(0:63, 0:3). Whereas the 2D transform module 304 operates on spatial blocks of pixels from the matched frames, the 1D transform module 308 operates on the temporal samples across the 2D transformed frame blocks at a given spatial index 0≦zz_index≦63. Therefore, there are sixty-four (64) 1D transforms for each set of four (4) 8×8 blocks.

As indicated above, the 1D Transform used for the VDN system embodiment 200 c-1 is a modified three-level, 1D Haar transform, though not limited to a Haar-based transform or three levels. That is, in some embodiments, other 1D transforms using other levels, wavelet-based or otherwise, may be used, including DCT, WHT, DWT, etc., with one of the goals comprising configuring the samples into filterable frequency bands. Before proceeding with processing of the overlapped block processing module 350, and in particular, 1D transformation, attention is re-directed to FIGS. 8A-8D, which illustrates various steps in the modification of a 1D Haar transform in the context of the reduction in frame matching described in association with FIGS. 2A-2C. It should be understood that each filter in the evolution of the 1D Haar shown in respective FIGS. 8A-8D may be a stand-alone filter that can be used in some VDN system embodiments. A modified Haar wavelet transform is implemented by the 1D transform module 308 (and the inverse in inverse 1D transform module 312) for the temporal dimension that enables frame collapsing in the manner described above for the different embodiments. In general, a Haar wavelet transform in one dimension transforms a 2-element vector according to the following equation:

$\begin{matrix} {{{\begin{pmatrix} {y(1)} \\ {y(2)} \end{pmatrix} = {T \cdot \begin{pmatrix} {x(1)} \\ {x(2)} \end{pmatrix}}},{where}}{T = {\frac{1}{\sqrt{2}}{\begin{pmatrix} 1 & 1 \\ 1 & {- 1} \end{pmatrix}.}}}} & {{Eq}.\mspace{14mu} (19)} \end{matrix}$

From Eq (19), it is observed that the Haar transform is a sum-difference transform. That is, two elements are transformed by taking their sum and difference, where the term 1/√{square root over (2)} is energy preserving, or normalization. It is standard in wavelet decomposition to perform a so-called “critically sampled full dyadic decomposition.”

A signal flow diagram 800A for the Haar transform, including the forward and inverse transforms, is shown in FIG. 8A. The signal flow diagrams 800A, 800B, 800C, or 800D in FIGS. 8A-8D are illustrative of example processing (from top-down) of 2D transform samples that may be implemented collectively by the 1D transform module 308 and the inverse 1D transform module 312. The signal flow diagram 800A is divided into a forward transform 802 and an inverse transform 804. The normalizing term 1/√{square root over (2)} may be removed if the transform is resealed on inverse (e.g., as shown in FIGS. 8A-8D by factors of four (4) and two (2) with ×2 and ×4, respectively, in the inverse transform section 804). In addition, while FIG. 8A shows the inverse Haar transform 804 following directly after the forward transform 802, it should be appreciated in the context of the present disclosure that in view of the denoising methods described herein, thresholding operations (not shown) may intervene in some embodiments between the forward transform 802 and the inverse transform 804.

In a dyadic wavelet decomposition, a set of samples are “run” through the transformation (e.g. as given by Eq. (19)), and the result is subsampled by a factor of two (2), known in wavelet theory as being “critically sampled.” Using eight (8) samples (e.g., 2D transformed, co-located samples) as an example in FIG. 8A, the samples b0 through b7 are transformed in a first stage 806 by Eq. (19) pair-wise on [b0 b1], [b2 b3], . . . [b6 . . . b7], producing the four (4), low frequency, sum-subband samples [L00, L01, L02, L03] and four (4), high frequency, difference-subband samples [H00, H01, H02, H03]. Since half the subbands are low-frequency, and half are high-frequency, the result is what is referred to as a dyadic decomposition. An eight (8) sample full decomposition continues by taking the four (4), low-frequency subband samples [L00, L01, L02, L03] and running them through a second stage 808 of the Eq. (19) transformation with critical sampling, producing two (2) lower-frequency subbands [L10, L11] and two (2) higher frequency subbands [H10, H11]. A third stage 610 on the two (2) lowest frequency samples completes the full dyadic decomposition, and produces [L20, H20].

The 1D Haar transform in FIG. 8A enables a forward transformation 802 and inverse transformation 804 when all samples (e.g., bd(i, j, 0:7)) are retained on output. This is the case for a 3D accumulation buffer. However, as discussed hereinabove, the output of the 2D+1 accumulation buffer (see FIGS. 2A-2B) requires only bd(i, j, 4) and bd(i, j, 7). Therefore, simplification of the flow diagram of 800A, where only the bd(i, j, 4) and bd(i, j, 7) are retained, results in the flow diagram denoted as 800B and illustrated in FIG. 8B.

In FIG. 8B, since bd(i, j, 4) and bd(i, j, 7) are the desired outcome, the entire left-hand side of the transformation process requires only the summation of the first four (4) samples b(i, j, 0:3). As described below, this summation may occur outside the 1D transform (e.g., as part of the frame matching process). On the right side, there has been a re-ordering of the samples when compared to the flow diagram of FIG. 8A (i.e., [b4 b5 b6 b7] to [b4 b7 b6 b5]). In addition, only the sum of b(i, j, 5) and b(i, j, 6) is required (not a subtraction). Accordingly, by using this simplified transform in flow diagram 800B, with sample reordering, and frame-matching the sum of the first four (4) frames to the reference frame F4(t), the first four (4) frames may be collapsed into a single frame. For frames 5 and 6, an assumption is made that both frames have been frame matched to the reference producing M5(t) and M6(t), and hence those frames may be summed prior to (e.g., outside) the 1D transform.

When the summing happens outside the 1D transform, the resulting 1D transform is further simplified as shown in the flow diagram 800C of FIG. 8C, where b0+b1+b2+b3 represents the blocks from the frame-matched sum of frames F0(t) through F3(t), that is MSUM0123(t), prior to the 1D transform, and b5+b6 represents the sum of blocks b(i, j, 5) and b(i, j, 6) from frame-matched and summed frames M5(t) and M6(t), that is MSUM56(t), the summation implemented prior to the 1D transform. Note that for 2D+1 accumulation embodiments corresponding to Haar modifications corresponding to FIGS. 8B and 8C, there is a re-ordering of samples such that b7 is swapped in and b5 and b6 are moved over.

Referring to FIG. 8D, shown is a flow diagram 800D that is further simplified based on a 2D accumulation buffer, as shown in FIG. 2C. That is, only one input sample, bd4, has been retained on output to the 2D accumulation buffer. Note that in contrast to the 2D+1 accumulation buffer embodiments where sample re-ordering is implemented as explained above, the Haar modifications corresponding to FIG. 8D involve no sample re-ordering.

Continuing now with the description pertaining to 1D transformation in the overlapped block processing module 350, and with reference to FIG. 3, at each zz_index, the 1D transform 308 processes the four (4) samples bs(zz_index, 0:3) to produce bhaar(0:63, 0:3), which includes Haar subbands [L20, H20, H02, H11]. The first index is from the stages 0, 1, 2, so L20 and H20 are from the third stage 810 (FIG. 8D), H02 is from the first stage 806 (FIG. 8D), and H11 is from the second stage (808). These Haar subbands are as illustrated in FIG. 8D and are further interpreted with respect to the matched frames as follows:

L20: summation of all matched blocks b(i,j, 0:7);

H20: difference between matched blocks in MSUM0123(t) and the total sum of matched blocks in M4(t), M5(t) and 2×MSUM67(t);

H02: For 2D+1 Accumulation Buffer (FIG. 8C), difference between matched blocks b4 and b7 from frames M4(t), and M7(t), respectively. For 2D Accumulation Buffer (FIG. 8D), difference between matched blocks b4 and b5 from frames M4(t), and M5(t), respectively.

H11: For 2D+1 Accumulation Buffer (FIG. 8C), difference between sum (b4+b7) matched blocks from M4(t) and M7(t) respectively, and 2×MSUM56(t). For 2D Accumulation Buffer (FIG. 8D), difference between sum (b4+b5) matched blocks from M4(t) and M5(t) respectively, and 2×MSUM56(t).

With reference to FIG. 9, shown is a schematic diagram 900 that conceptually illustrates the various temporal mode selections that determine whether 3D or 2D thresholding is enabled, and whether Haar or spatial subbands are thresholded for 3D and 2D, respectively. As shown, the selections include MODE8, BAK4, FWD4, and SPATIAL, explained further below. The temporal mode selections make it possible for the VDN systems 200 to adapt to video scenes that are not temporally correlated, such as scene changes, or other discontinuities (e.g., a viewer blinks his or her eye or turns around during a scene that results in the perception of a discontinuity, or discontinuities associated with a pan shot, etc.) by enabling a determination of which frames of a given temporal sequence (e.g., F0(t)-F7(t)) can be removed from further transform and/or threshold processing. The TemporalMode selections are as follows:

For TemporalMode==MODE8 or TemporalMode==SPATIAL: (no change). In other words, for TemporalMode set to MODE8 or SPATIAL, there is no need to preprocess the samples before the 1D transform. For FWD4 or BAK4 temporal modes, the samples undergo preprocessing as specified below.

For TemporalMode==FWD4: (Input sample b0+b1+b2+b3 from MSUM0123(t) is set equal to zero);

For TemporalMode==BAK4: (Input sample b4 set equal to 4*b4);

In one embodiment, a temporal mode module 302 computes TemporalMode after the 2D transform is taken on the 8×8×4 set of blocks. The TemporalMode takes on one of the following four values:

(a) SPATIAL: when the TemporalMode is set to SPATIAL, 2D (spatial) thresholding takes place after the 2D transform on each 2D block bs(0:63, t) 0≦t≦3 separately to produce bst(0:3, t). In other words, under a spatial temporal mode, there is no 1D transformation or thresholding of 3D blocks (temporal dimension is removed for this iteration). If the Temporal Mode is not set to SPATIAL, then bst(0:63, t) is set to bs(0:63, t) (pass-through).

(b) FWD4: when the TemporalMode is set to FWD4, right-sided (later) samples from M4(t), M5(t) and MSUM67(t) are effectively used, and samples from the left (earlier) side, in MSUM0123(t), are not used.

(c) BAK4: when the TemporalMode is set to BAK4, left-sided (earlier) samples from MSUM0123(t) and M4(t) are effectively used, and samples from the right (later) side, in M5(t) and MSUM67(t), are not used.

(d) MODE8: when the TemporalMode is set to MODE8, all samples are used. The TemporalMode is computed for every overlapped set of blocks (e.g., its value is computed at every overlapped block position). Therefore, implicitly, TemporalMode is a function of i, j, so TemporalMode(i, j) denotes the value of TemporalMode for the i, j-th pixel position in the overlapped block processing. The shorthand, “TemporalMode” is used throughout herein with the understanding that TemporalMode comprises a value that is computed at every overlapped block position of a given frame to ensure, among other reasons, proper block matching is achieved. In effect, the selected temporal mode defines the processing (e.g., thresholding) of a different number of subbands (e.g., L20, H20, etc.).

Having described the various temporal modes implemented in the VDN systems 200, attention is now directed to a determination of which temporal mode to implement. To determine TemporalMode, the SubbandSAD is computed (e.g., by the 2D transform module 304 and communicated to the temporal mode module 302) between the blocks bs(0:63, k) and bs(0:63, 1) for 0≦k≦3 (zero for k=1), which establishes the closeness of the match of co-located blocks of the inputted samples (from the matched frames), using the low-frequency structure of the blocks where the signal can mostly be expected to exceed noise. Explaining further, the determination of closeness of a given match may be obscured or skewed when the comparison involves noisy blocks. By rejecting noise, the level of fidelity of the comparison may be improved. In one embodiment, the VDN system 200 c-1 effectively performs a power compaction (e.g., a forward transform, such as via DCT) of the blocks at issue, whereby most of the energy of a natural video scene are power compacted into a few, more significant coefficients (whereas noise is generally uniformly distributed in a scene). Then, a SAD is performed in the DCT domain between the significant few coefficients of the blocks under comparison (e.g., in a subband of the DCT, based on a predefined threshold subband SAD value, not of the entire 8×8 block), resulting in removal of a significant portion of the noise from the computation and hence providing a more accurate determination of matching.

Explaining further, in one embodiment, the subbandSAD is computed using the ten (10) lowest frequency elements of the 2D transformed blocks bs(0:9, 0:3) where the frequency order low-to-high follows the zig-zag scanning specified hereinbefore. In some embodiments, fewer or greater numbers of lowest frequency elements may be used. Accordingly, for this example embodiment, the SubbandSAD(k) is given by the following equation:

$\begin{matrix} {{{{SubbandSAD}\mspace{11mu} (k)} = {\sum\limits_{z = 0}^{9}{{{{bs}\left( {z,k} \right)} - {{bs}\left( {z,1} \right)}}}}},} & {{Eq}.\mspace{14mu} (20)} \end{matrix}$

where 0≦k≦3, and SubbandSAD(1)=0.

Integer counts SubbandFWDCount4, SubbandBAKCount4 and SubbandCount8 may be defined as follows:

$\begin{matrix} {{{SubbandCountFWD}\mspace{14mu} 4} = {\sum\limits_{k = 1}^{3}{{SetToOneOrZero}\left( {{{SubbandSAD}\mspace{11mu} (k)} < {Tsubbandsad}}\; \right)}}} & {{Eq}.\mspace{14mu} \left( {21a} \right)} \\ {{{SubbandCountBAK}\mspace{11mu} 4} = {\sum\limits_{k = 0}^{1}{{SetToOneOrZero}\left( {{{SubbandSAD}\mspace{11mu} (k)} < {Tsubbandsad}}\; \right)}}} & {{Eq}.\mspace{14mu} \left( {21b} \right)} \\ {{{SubbandCount}\mspace{14mu} 8} = {\sum\limits_{k = 0}^{3}{{SetToOneOrZero}\left( {{{SubbandSAD}\mspace{11mu} (k)} < {Tsubbandsad}}\; \right)}}} & {{Eq}.\mspace{14mu} \left( {21c} \right)} \end{matrix}$

where the function SetToOneOrZero(x) equals 1 when its argument evaluates to TRUE, and zero otherwise, and Tsubbandsad is a parameter. In effect, Eqns. 21a-21c are computed to determine how many of the blocks are under the subband SAD threshold, and hence determine the temporal mode to be implemented. For instance, referring to Eq. 21c, for MODE8, the DCT of b0+b1+b2+b3 should be close enough in the lower frequencies to the DCT of b4 (and likewise, the DCT of b5 and b6+7 should be close enough in the lower frequencies to b4). Note that k=0 to k=3 since there is b0+b1+b2+b3, b4 (though k=1 is meaningless since the subband SAD of b4 with itself is zero), b5, and b6+7.

In Eq. 21a, for FWD4, the closeness of b4 with b5 and b6+7 is evaluated, so the numbering for k goes from 1-3 (though should go from 2 to 3 since 1 is meaningless as explained above). In Eq. 21b, numbering for k goes from 0 to 1, since only the zeroth sample is checked (i.e., the b0+1+2+3 sample, and again, 1 is meaningless since b4 always matches itself).

Accordingly, using SubbandCountFWD4, SubbandCountBAK4, and SubbandCount8, TemporalMode is set as follows:

If SubbandCount8==4, then TemporalMode=MODE8;

-   -   else if SubbandCountFWD4==3 then TemporalMode=FWD4;     -   else if SubbandCountBAK4==2 then TemporalMode=BAK4;     -   else TemporalMode=SPATIAL.         Note that this scheme favors FWD4 over BAK4, but if MODE8 is not         signaled, then only one of FWD4 or BAK4 can be satisfied anyway.

Thresholding is performed on the 2D or 3D transformed blocks during the overlapped block processing. For instance, when TemporalMode is set to SPATIAL, the 2D threshold module 306 is signaled, enabling the 2D threshold module 306 to perform 2D thresholding of the 2D transformed block bs(0:63, 1) from F4(t). According to this mode, no thresholding takes place on the three (3) blocks from MSUM0123(t), M5(t) or MSUM67(t) (i.e., there is no 2D thresholding on bs(0:63, 0), bs(0:63, 2), bs(0:63, 3)).

Reference is made to FIG. 10, which is a schematic diagram 1000 that illustrates one example embodiment of time-space frequency partitioning by thresholding vector, T_(—)2D, and spatial index matrix, S_(—)2D, each of which can be defined as follows:

T_(—)2D(0:3): 4-element vector of thresholds

S_(—)2D(0:3,2): 4×2 element matrix of spatial indices

Together, T_(—)2D and S_(—)2D define the parameters used for thresholding the 2D blocks bs(0:63, 1). For only the 8×8 2D transformed block bs(0:63, 1), the thresholded block bst(0:63, 1) may be derived according to Eq. (22) below:

$\begin{matrix} {{{bst}\left( {z,t} \right)} = \left\{ \begin{matrix} 0 & \begin{matrix} {{{if}\mspace{14mu} {{{bs}\left( {z,1} \right)}}} < {{T\_}2{D(j)}\mspace{14mu} {and}}} \\ {{{S\_}2{D\left( {j,0} \right)}} \leq z \leq {{S\_}2{D\left( {j,1} \right)}}} \end{matrix} \\ {{bs}\left( {z,1} \right)} & {otherwise} \end{matrix} \right.} & {{Eq}.\mspace{14mu} (22)} \end{matrix}$

for j=0 . . . 3.

In Eq. (22), T_(—)2D(j) defines the threshold used for block 1, bs(0:63, 1) from M4(t), over a span of spatial indices S_(—)2D(j, 0) to S_(—)2D(j, 1) for j=0.3. Equivalently stated, elements of bs(S_(—)2D(j, 0): S_(—)2D(j, 1), 1) are thresholded by comparing the values of those elements to the threshold T_(—)2D(j), and the values in bs(S_(—)2D(j, 0): S_(—)2D(j, 1), 1) are set to zero when their absolute values are less than T_(—)2D(j). Note that none of the matched frames MSUM0123(t), MSUM67(t) or M5(t) undergo 2D thresholding, only blocks from M4(t), bs(0:63, 1).

The spatial index matrix S_(—)2D together with T_(—)2D define a subset of coefficients in the zig-zag scanned spatial frequencies as illustrated in FIG. 10. The 2D space has been reduced to 1D by zig zag scanning

Thresholding (at 3D threshold module 310) of the 3D transformed blocks bhaar(0:63, 0:3) output from 1D transform module 308 is performed when TemporalMode is set to either FWD4, BAK4 or MODE8. Otherwise, when TemporalMode is set to SPATIAL, the output of 3D thresholding module 310 (e.g., bhaart(0:63, 0:3)) is set to the input of the 3D thresholding module 310 (e.g., input equals bhaar(0:63, 0:3)) without modification. The 3D thresholding module 310 uses threshold vectors T_(—)3D(j) and spatial index matrix S_(—)3D(j, 0:1) defined hereinabove in 2D thresholding 306, except using eight (8) thresholds so 0≦j≦8.

An additional threshold vector TSUB(j,0:1) is needed for 3D thresholding 310, which defines the range of temporal subbands for each j. For example, TSUB(0,0)=0 with TSUB(0, 1)=1 along with T_(—)3D(0)=100 and S_(—)3D(0, 0)=0 and S_(—)3D(0, 1)=32 indicates that for j=0, 3D thresholding with the threshold of 100 is used across Haar subbands L20 and H20 and spatial frequencies 0 to 32.

Thresholding 310 of the 3D blocks is followed identically to the 2D thresholding 306 case following Eq. (22), but substituting T_(—)3D and S_(—)3D for T_(—)2D and S_(—)2D. For 3D thresholding 310, unlike 2D, all four (4) blocks bhaar(0:63, 0:3) are thresholded.

For MODE8, all Haar subbands are thresholded. For FWD4 and BAK4, only a subset of the Haar subbands is thresholded. The following specifies which subbands are thresholded according to TemporalMode:

If TemporalMode==MODE8 threshold [L20, H20, H02, H11] Haar Subbands;

If TemporalMode==FWD4 threshold [L20, H02, H11] Haar Subbands;

If TemporalMode==BAK4 threshold [L20, H20] Haar Subbands.

The temporal mode determinations described above are further facilitated by another preprocessing sub-system embodiment, referred to herein as the SCD sub-system 300B shown in FIGS. 3 and 5. In one embodiment, logic of the SCD sub-system 300 resides in the full pixel BM 516 as shown (FIG. 5), though one having ordinary skill in the art should appreciate that other locales are contemplated for the SCD sub-system functionality in some embodiments. Generally, scene change detection and handling are utilized for proper temporal mode decisions. During a scene change, for example, even if 99% of the temporal mode decisions are fairly optimal, there exists a chance of a few bad decisions bleeding into the denoised frame and becoming visible. In one embodiment, scene changes are detected for the F7 frame (see, e.g., FIGS. 2C and 4) during FULLBM (or an F8 and delayed one frame). In general, all modes are reverted to backward and spatial-only (no forward) during a scene change, and forward and spatial-only (no backward)—four (4) frames later—as the old scene shifts into F0 to F3. When the scene change is completely flushed (F0 on previous frame), then mode decision processing reverts to normal operation in the manner described above.

More specifically, scene change detection occurs during full pixel block matching (e.g., corresponding to full pixel BM 516), defined above in association with FIG. 5, for luma only (chroma reuses the luma scene change detect, although in some embodiments, not limited to exclusively re-using luma). For each of the 8×8 luma blocks in full pixel block matching, if the final SAD in Eq. (14) is above a defined threshold, TSAD_SCENE_DETECT_THRESH, a counter is incremented for the frame. When the counter exceeds another threshold, T_NUM_SAD_ABOVE_SCENE_DETECT_THRESH, a scene change detection is triggered. The T_NUM_SAD_ABOVE_SCENE_DETECT_THRESH parameter is set as some percentage of the total 8×8 blocks in the frame (e.g., 40%), though in some embodiments, other criteria may be used for the setting configuration. Although the discussion above is described in the context of incrementing a counter and triggering of scene change detection responsive to “exceeding” certain thresholds, one having ordinary skill in the art should understand that other event triggering criteria (e.g., greater than or equal to, etc.) may be employed in some embodiments.

In one embodiment, scene change detection is triggered only during the F7→F6 block matching, since this is the most distant frame later in time from F4. Also, since block matching proceeds for both fields independently in interlaced video, a scene change detection is triggered whenever either of the fields detects a scene change. FIG. 11 shows a diagram 1100 of an index or table of matched frames 1102 (M0, M1, . . . M7) and a corresponding scene change detection mask (SCDM) 1104 maintained by logic of the SCD sub-system 300B. When a scene change is detected, a bit is set in the SCDM 1104. In this example embodiment, the SCDM 1104 comprises a mask which indicates the scene change detection history for the current time and previous seven (7) frame times. For each frame processing interval, this mask 1104 is shifted to the left one bit and a new bit is set on the right, denoting the scene change status (scene change detected) for the current M7. If matching F8→F7 (and delaying, instead of F7→F6), then everything is delayed one frame with equivalent effect. It should be understood by one having ordinary skill in the art in the context of the present disclosure that the use of eight (8) frames is only one example embodiment used for illustrative purposes, and other quantities of frames may be used, enabling larger or smaller masks than the mask 1104 shown in FIG. 11.

From the description above, it should be appreciated that the SCD sub-system 300B implements a scene change detection process that yields the SCDM 1104, the SCDM 1104 indicating the scene change history for frames M0 through M7. The SCDM 1104 is communicated to the temporal mode module 302. With a bit of the SCDM 1104 set for a given window of frames, the temporal mode decision described above in association with FIG. 9 is altered as given in the example pseudocode below:

Mode = GetTemporalMode  if Scene Change Mask Forward Bits Set  {   if Mode == BI8   {     Mode = BAK4   }   else if Mode == FWD4   {     Mode = SPATIAL   }  }  if Any Scene Change Mask Backward Bits Set  {   if Mode == BI8   {   Mode = FWD8   }   else if Mode == BAK4   {     Mode = SPATIAL   } }

Note that chroma processing uses the luma SCDM 1104 (e.g., the mask 1104 is set once in the luma pixel BM process). Addressing the cooperation between the temporal mode determinations described above in association with FIG. 9 and the SCD sub-system 300B, one method embodiment comprises first determining the temporal mode in the manner as described in association with FIG. 9. Then, if the SCDM 1104 has any forward bits set, in accordance with the pseudocode hereinabove, the mode is reverted to backward only or spatial only modes. If the SCDM 1104 has any backward bits set, then the mode is reverted to forward only or spatial mode. Note that both forward and backward bits may be set for very fast scene changes (e.g., less than eight (8) frames), during a continual cross-fade, etc. If no bits are set in the SCDM 1104, then the temporal mode as initially determined is left unaltered.

Having described example embodiments of thresholding in VDN systems, attention is again directed to FIG. 3 and inverse transform and output processing. Specifically, inverse transforms include the inverse 1D transform 312 (e.g., Haar) followed by the inverse 2D transform (e.g., AVC integer DCT), both described hereinabove. It should be understood by one having ordinary skill in the art that other types of transforms may be used for both dimensions, or a mix of different types of transforms different than the Haar/AVC integer combination described herein in some embodiments. For a 1D Haar transform, the inverse transform proceeds as shown in FIG. 8D and explained above.

The final denoised frame of FD4(t) using the merged accumulation buffers is specified in Eq. (23) as follows:

$\begin{matrix} {{{FD}\; 4\left( {i,j} \right)} = \frac{A\left( {i,j} \right)}{W\left( {i,j} \right)}} & {{Eq}.\mspace{14mu} (23)} \end{matrix}$

For uniform weighting where w(i,j)=1 for all overlapped blocks, Eq. (23) amounts to a simple divide by 16 (for step size=2). However, if selectively omitting blocks, then Eq. (23) amounts to division by a number 1≦W(i,j)≦16. After the 2D inverse transform 314 follows the 1D inverse transform 312, the block bd(i,j,1) represents the denoised block of F4(t). This denoised block is accumulated (added into) in the A4(t) accumulation buffer(s) 360 (e.g., accumulates the denoised estimates via repeated loops back to the 2D transform module 304 to index or shift in pixels to repeat the processing 350 for a given reference frame), and then output via normalization block 370.

Having described various preprocessing sub-systems of the example VDN systems 200 disclosed herein, it should be appreciated that one method embodiment 1200A, implemented by the field-frame processing sub-system 300C in conjunction with an overlapped block processing module 350 and shown in FIG. 12A, comprises providing a field-frame map by partitioning a block matched frame into plural non-overlapping superblocks (1202); designating each of the plural superblocks of the field-frame map as either field or frame (1204); comparing an overlapped superblock to first plural superblocks of the field-frame map (1206); and field processing by overlapped block processing logic two overlapped blocks of the overlapped superblock if one of the first plural blocks intersected by the overlapped superblock has a field designation, otherwise frame processing, by the overlapped block processing logic, the two overlapped blocks of the overlapped superblock (1208).

Another method embodiment, 1200B, implemented by the field-frame processing sub-system 300C in conjunction with an overlapped block processing module 350 and shown in FIG. 12B, comprises partitioning a block matched reference frame into plural n×m non-overlapping pixel superblocks, where n and m are non-negative integer numbers (1210); designating each of the n×m pixel superblocks as field or frame (1212); and field processing by overlapped block processing logic two n×n blocks of an n×m overlapped superblock if one of first plural n×m blocks intersected by the overlapped superblock has a field designation, otherwise frame processing, by the overlapped block processing logic, the two n×n blocks of the overlapped superblock (1214).

Another method embodiment 1300, shown in FIG. 13, implemented by the SCD sub-system 300B, comprises receiving noise-filtered plural blocks of a first frame and noise-filtered plural blocks of a second frame (1302); for each of the plural blocks to be matched, determining whether an indication of closeness in match between the each of the plural blocks exceeds a first threshold (1304); incrementing a counter value each time the first threshold is exceeded for closeness of the block matching of a particular block (1306); determining whether the counter value exceeds a second threshold, the exceeding of the second threshold indicating that a defined quantity of blocks has exceeded the first threshold (1308); and responsive to determining that the counter value exceeds the second threshold, triggering a scene change detection (1310).

Another method embodiment 1400, shown in FIG. 14, implemented by the SMC sub-system 300A, comprises receiving at a frame matching module a first frame comprising first plural blocks and plural frames that each comprise a plurality of blocks to be matched to the first plural blocks of the first frame, the first plural blocks and the plurality of blocks comprising luma blocks (1402); for each of the frame pair matchings, selecting one border configuration among a plurality of border configurations, the border configuration selected for the each of the frame pair matchings unique (1404); appending a border of pixels to the frames of the each of the frame pair matchings based on the selected border configuration (1406); and block matching the first plural blocks with the plurality of blocks (1408).

Any process descriptions or blocks in flow charts or flow diagrams should be understood as representing modules, segments, or portions of code which include one or more executable instructions for implementing specific logical functions or steps in the process, and alternate implementations are included within the scope of the present disclosure in which functions may be executed out of order from that shown or discussed, including substantially concurrently or in reverse order, depending on the functionality involved, as would be understood by those reasonably skilled in the art. In some embodiments, steps of a process identified in FIGS. 12A-14 using separate boxes can be combined. Further, the various steps in the flow diagrams illustrated in conjunction with the present disclosure are not limited to the architectures described above in association with the description for the flow diagram (as implemented in or by a particular module or logic) nor are the steps limited to the example embodiments described in the specification and associated with the figures of the present disclosure. In some embodiments, one or more steps may be added to one or more of the methods described in FIGS. 12A-14, either in the beginning, end, and/or as intervening steps.

It should be emphasized that the above-described embodiments of the present disclosure are merely possible examples of implementations, merely set forth for a clear understanding of the principles of the VDN systems and methods and their associated sub-systems. Many variations and modifications may be made to the above-described embodiment(s) without departing substantially from the spirit and principles of the disclosure. Although all such modifications and variations are intended to be included herein within the scope of this disclosure and protected by the following claims, the following claims are not necessarily limited to the particular embodiments set out in the description. 

1. A method, comprising: providing a field-frame map by partitioning a block matched frame into plural non-overlapping superblocks; designating each of the plural superblocks of the field-frame map as either field or frame; comparing an overlapped superblock to first plural superblocks of the field-frame map; and field processing by overlapped block processing logic two overlapped blocks of the overlapped superblock if one of the first plural blocks intersected by the overlapped superblock has a field designation, otherwise frame processing, by the overlapped block processing logic, the two overlapped blocks of the overlapped superblock.
 2. The method of claim 1, wherein the pixel blocks comprise luma pixel blocks.
 3. The method of claim 1, wherein designating the superblock as a field or frame comprises subtracting plural luminance intensity values between successive lines of a frame and successive lines of a field, comparing the difference values corresponding to the frame and the field with a defined threshold value, and designating based on the comparison to the defined threshold value.
 4. The method of claim 1, wherein field processing comprises simultaneously processing the two overlapped blocks configured as two vertically interleaved blocks of the overlapped superblock for luma.
 5. The method of claim 1, wherein frame processing comprises processing the two overlapped blocks configured as two vertically adjacent top and bottom frame blocks of the overlapped superblock for luma.
 6. The method of claim 1, wherein the first plural superblocks of the field-frame map are each overlapped at least in part by the overlapped superblock.
 7. The method of claim 1, wherein comparing comprises receiving the field-frame map and a coordinate position of the overlapped superblock.
 8. The method of claim 1, further comprising chroma overlap block processing, wherein the chroma overlap block processing is based on two n×n fields spanning 2×n pixels vertically, where n is a non-negative integer number.
 9. The method of claim 1, wherein designating comprises designating each of the plural superblocks as frames for a progressive video input.
 10. The method of claim 1, wherein intermediate denoised pixel blocks output from the block processing logic are signaled to be accumulated according to the field or frame designations.
 11. A system, comprising: block matching logic configured to provide a block matched frame; field-frame mapping logic configured to provide a field-frame map by partitioning the frame into plural non-overlapping superblocks, the field-frame mapping logic further configured to designate each of the superblocks as either field or frame; field-frame logic configured to compare an overlapped superblock to first plural superblocks of the field-frame map; and overlapped block processing logic configured to: field process two blocks of the overlapped superblock if one of the first plural superblocks intersected by the overlapped superblock has a field designation; and frame process the two blocks of the overlapped superblock if one of the first plural superblocks intersected by the overlapped superblock has a frame designation.
 12. The system of claim 11, wherein the field-frame mapping logic is further configured to designate each of the superblocks as a field or frame by subtracting plural luminance intensity values between successive lines of a frame and successive lines of a field, comparing the difference values corresponding to the frame and the field with a defined threshold value, and designating based on the comparison to the defined threshold value.
 13. The system of claim 11, wherein the overlapped block processing logic is configured to field process by simultaneously processing two vertically interleaved blocks of the overlapped superblock for luma.
 14. The system of claim 11, wherein the overlapped block processing logic is configured to frame process by processing two vertically adjacent top and bottom frame blocks of the overlapped superblock for luma.
 15. The system of claim 11, wherein the field-frame logic is configured to receive the field-frame map and a coordinate position of the overlapped superblock.
 16. The system of claim 11, wherein the first plural superblocks of the field-frame map are each overlapped at least in part by the overlapped superblock.
 17. The system of claim 11, further comprising chroma overlap block processing logic, wherein the chroma overlap block processing logic is configured to implement chroma overlap block processing based on two n×n fields spanning 2×n pixels vertically, where n is a non-negative integer number.
 18. A method, comprising: partitioning a block matched reference frame into plural n×m non-overlapping pixel superblocks, where n and m are non-negative integer numbers; designating each of the n×m pixel blocks as field or frame; and field processing by overlapped block processing logic two n×n blocks of an n×m overlapped superblock if one of first plural n×m superblocks intersected by the overlapped block has a field designation, otherwise frame processing, by the overlapped block processing logic, the two n×n blocks of the overlapped superblock.
 19. The method of claim 18, wherein field processing comprises simultaneously processing the two overlapped blocks configured as two vertically interleaved blocks of the overlapped superblock for luma.
 20. The method of claim 18, wherein frame processing comprises processing the two overlapped blocks configured as two vertically adjacent top and bottom frame blocks of the overlapped superblock for luma. 